Subject | Re: Drop table causes an error |
---|---|
Author | Alexander V.Nevsky |
Post date | 2004-05-05T17:40:37Z |
--- In firebird-support@yahoogroups.com, "andrew_abyzov" <abyzov@b...>
wrote:
Seems you are violating general rule - most of DDL statements should
be performed in exclusive access mode (note several connections from
the same computer violates this rule too) and in this exclusive
connection should be active only one transaction - those in which
context this DDL statement is performed. Some DDL, such as procedures
and triggers creation/alteration/dropping can be performed in
multi-user environment, but result is'nt very predictable - on Classic
users connected before this DDL will use old instatnces of altered
procedure, after - new. AFAIR on SuperServer all users should
re-connect to activate new instances of procedures.
Best regards,
Alexander
wrote:
> I'm using Firebird 1.5 Final Release (Win32).Hmm, this index should'nt cause fail of attempt to drop table.
>
> The DDL is as follows:
>
> CREATE TABLE L_WORKSELENA (
> NUM_REC SMALLINT,
> KOD CHAR(8),
> KLASS_STR VARCHAR(50),
> ED_IZM VARCHAR(10),
> ARTICUL VARCHAR(20),
> KOL NUMERIC(15,5),
> CENA NUMERIC(15,5),
> SUMMA NUMERIC(10,2)
> );
>
> CREATE INDEX IX_L_WORKSELENA_NUM_REC ON L_WORKSELENA (NUM_REC);
>
> The components used are IB Xpress 6.08.
Seems you are violating general rule - most of DDL statements should
be performed in exclusive access mode (note several connections from
the same computer violates this rule too) and in this exclusive
connection should be active only one transaction - those in which
context this DDL statement is performed. Some DDL, such as procedures
and triggers creation/alteration/dropping can be performed in
multi-user environment, but result is'nt very predictable - on Classic
users connected before this DDL will use old instatnces of altered
procedure, after - new. AFAIR on SuperServer all users should
re-connect to activate new instances of procedures.
Best regards,
Alexander