Subject | Re: [Firebird-Java] Possible bug in Firebird1.5.2Classic(cross-post) |
---|---|
Author | David Johnson |
Post date | 2005-08-08T12:10:13Z |
On Mon, 2005-08-08 at 13:56 +0200, Roman Rokytskyy wrote:
A 24x7 application is deployed and the users try to run it. Something
is not quite right, so new DML is promoted and new DDL is submitted to
the DBA, who drops and recreates the table. The application
configuration is updated but the app never closes. This can't be that
unusual - I can't be the only one here thinking 24x7 uptime.
> > The usage pattern in _this_ example is unusual because it is a testcaseNot that unusual.
> > that has not got past create and destroy objects.
>
> Under "unusual" I mean that you prepare statements for the newly created
> table in both connections, then you close them, then you drop table in one
> connection and then you prepare a statement referencing that table in other
> connection.
>
> Roman
A 24x7 application is deployed and the users try to run it. Something
is not quite right, so new DML is promoted and new DDL is submitted to
the DBA, who drops and recreates the table. The application
configuration is updated but the app never closes. This can't be that
unusual - I can't be the only one here thinking 24x7 uptime.