Subject | Re: [IB-Architect] SQL Scripts |
---|---|
Author | Olivier Mascia |
Post date | 2001-12-11T18:58:13Z |
Hello,
Marco Lauria wrote:
Conceptually transactions can span multiple databases, so eventually multiple
servers.
Just as a script could manipulate multiple databases, so multiple
servers.
Scripts, if defined as a sequence of valid SQL statements, eventually
interspersed with additional environmental statements, are a thing which
would gain from being standardized among the various components, but
which is conceptually tied to the client-side.
--
Olivier Mascia <om@...>
Marco Lauria wrote:
> It should be on the server, for the command typical of the serverNo no and no (well that's my very personal opinion).
> so for all the commands except CONNECT, DROP AND CREATE.
> I don't include COMMIT or ROLL BACK as these regards the server
> and not the client.
Conceptually transactions can span multiple databases, so eventually multiple
servers.
Just as a script could manipulate multiple databases, so multiple
servers.
Scripts, if defined as a sequence of valid SQL statements, eventually
interspersed with additional environmental statements, are a thing which
would gain from being standardized among the various components, but
which is conceptually tied to the client-side.
--
Olivier Mascia <om@...>