> >> In my Firebird 1.5 database, I have a table WORK which works pretty
> much
> >> like Firebird 2.1's global temporary table, except that it's
> contents
> >> are deleted by application rather than the server (when an
> application
> >> ends, it DELETEs all records WHERE connection_id=<some number>, and
> >> there are regular DELETEs without conditions to get rid of possibly
> >> forgotten values).
> >>
> >> Is it possible to change this "real table" to global temporary table
> of
> >> Firebird 2.1 without dropping and re-creating it? I have in mind
> >> something like changing its RDB$RELATION_TYPE to 4 - would that be
> >> sufficient for "temporarizing" the table?
> >>
> > Are you talking about changing RDB$RELATION_TYPE on a Firebird 1.5
> > server? Then of course not: this functionality was created in later
> versions
> > of
> > Firebird.
> >
>
> Application runs on Firebird 1.5 and needs to continue doing so. But
> users will move to Firebird 2.1 in the future along with their
> databases.
>
> > And even in a Firebird 2.1 databases, I very much doubt that setting
> a new
> > value to that column would work.
> >
> It does, actually. At least in current 2.1. The question is, is it
> intentional or accidental?
> > What do you have against re-creating it properly?
> >
>
> About a hundred depending procedures, which have their own dependencies
> and so on...
>
> Pepak
>

a decent admin tool will create a re-create script including all
dependencies.
Alan