Since some people love our parser, I've prepared some stunning examples for
Christmas. Please don't try them on your production server, unless you're
looking for a scapegoat to have forced vacations (by being fired).

create domain what_is.my_name int;

create table our(parser.sucks char(10));

create table I_will(screw_you.* long float);

create view the_same(history.*) as select 1 from rdb$database;

select
t
.
*
from
rdb$database
t
;

select(0)from rdb$database;

select(0.*.0)from rdb$database;

create table t(a int);
grant update(z.*) on t to public;
grant update(z.a) on t to public;

create domain poor.* blob;

/* The following three are valid albeit strange. However, the SQL standard
seems to consider 2 & 3 invalid because you can't qualify the assigned
field;
it belongs to the table being updated by definition. */
update t t set a=0;

update t u set u.a=0;

update t u set u.a=t.a;

While talking to a gipsy woman, she told me "I see a lot of bugs in your
future". Maybe my future came too fast.
:-)

"A bug is a bug while in beta testing; once it makes its way in production,
it's a disaster".

"You should not only count the number of bugs; you should measure the
quality of the bugs. Experienced programmers create more sophisticated
bugs".

"SW engineering is a discipline, a fake science that provides estimation
tools for the performance of a project, measured in bugs per months".

"A bug has the same basic rights than a pet. Some programmers indeed keep
the same bugs for years and refuse to dispose of them".

"A bug reaches the status of a feature when it's documented with a couple of
workarounds in the official manual".

"No matter what you do, bugs will survive, mutate, thrive and strike back".
- Murphy.

On the other hand, there's always hope and this is the main reason we fight
SW bugs as hard as possible, to make life easier and more pleasant.

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing