Subject | Re: [Firebird-Architect] RFC: Proposal for the implementation |
---|---|
Author | Ann W. Harrison |
Post date | 2004-11-26T19:27:07Z |
At 04:09 PM 11/24/2004, Arno Brinkman wrote:
tables. Though, of course, maintaining the inherited definition
would be messy if one wanted to backup and restore the database.
Having a table that changed format and contents when restored from
a backup would be ... well ... odd.
On the other hand, I would like to have temporary tables that
use a subquery definition to be created to match the current
results of the subquery and to have their data loaded on reference.
Creating a new table instance - which is what a temporary table
is, essentially - using data that was current when the table was
defined seems ill-considered. Not to mention messy as hell,
regardless of the implementation chosen.
I will read the new standard closely and try to understand the
intention of the committee...
Regards,
Ann
>In my understanding the "inherited definition" is only taken at definitionFine for permanent tables, but not terribly useful for temporary
>time and what happens after that is not important.
tables. Though, of course, maintaining the inherited definition
would be messy if one wanted to backup and restore the database.
Having a table that changed format and contents when restored from
a backup would be ... well ... odd.
On the other hand, I would like to have temporary tables that
use a subquery definition to be created to match the current
results of the subquery and to have their data loaded on reference.
Creating a new table instance - which is what a temporary table
is, essentially - using data that was current when the table was
defined seems ill-considered. Not to mention messy as hell,
regardless of the implementation chosen.
I will read the new standard closely and try to understand the
intention of the committee...
Regards,
Ann