Subject | Re: [Firebird-Architect] for discussion Transient Data Set |
---|---|
Author | Ann W. Harrison |
Post date | 2005-01-12T16:56:57Z |
Leyne, Sean wrote:
the temporary file could be a RAM file, which the database can't. The
clean up of a temporary file is instant and automatic.
Relation objects and their various relatives. The system tables are a
bootstrap mechanism. The earlier discussion of temporary tables
provides a general architecture for mapping a relation to a different file.
Regards,
Ann
>Two reasons. Clean-up and performance. The performance reason is that
>
> Why not store them in the database file itself?
the temporary file could be a RAM file, which the database can't. The
clean up of a temporary file is instant and automatic.
> As I see it, it would simplify the implementation since the engine wouldAfter the first reference, the engine gets all its information from the
> see the TDS just like a real table (registered in RDB$RELATIONS), and
> all existing table functionality would be supported.
Relation objects and their various relatives. The system tables are a
bootstrap mechanism. The earlier discussion of temporary tables
provides a general architecture for mapping a relation to a different file.
Regards,
Ann