At 04:44 AM 12/1/2004, Nando Dessena wrote:

>with the limitations above, not much. But I am a little lost as to how
>the original requirements from Volker Rehn generated this whole
>discussion about SQL standard temporary tables.

That's easy. We set about the produce a design for temporary
tables. Temporary tables are part of the SQL standard, so if
we're going to design them, we must follow the syntax and
semantics of the standard. Right, that rule doesn't apply to
MSSQL or MySQL, but I consider their attitude toward standards
unprofessional.

If we're a serious database builder and claim standard compliance,
features are either standard compliant and use standard language
with standard semantics, or they are non-standard and use language
that is not part of the standard and our own semantics. We don't
do a Humpty-Dumpty(see below) and insist that standard syntax follow
our own semantics.

>Scoped table/cursor variables (with table/cursor as a
>datatype) are what Firebird needs IMHO.

OK, that's an interesting discussion. What's a scoped
cursor variable? What does it do, how is it created,
how is it destroyed? Can it be extended, either in content
or in definition (e.g. adding columns)? Can it be preserved?
How is it different from a scoped table variable? What does
it mean for a table to be a datatype?


Regards,


Ann

From Through the Looking Glass by Lewis Carroll

`And only one for birthday presents, you know. There's glory for you!'

`I don't know what you mean by "glory",' Alice said.

Humpty Dumpty smiled contemptuously. `Of course you don't -- till I tell
you. I meant "there's a nice knock-down argument for you!"'

`But "glory" doesn't mean "a nice knock-down argument",' Alice objected.

`When I use a word,' Humpty Dumpty said, in rather a scornful tone, `it
means just what I choose it to mean -- neither more nor less.'

`The question is,' said Alice, `whether you can make words mean so many
different things.'

`The question is,' said Humpty Dumpty, `which is to be master -- that's all.'