Subject | Re: [ib-support] Dropping tables and indexes in IB7 |
---|---|
Author | Brian L. Juergensmeyer |
Post date | 2003-01-29T18:22:40Z |
Hi, Martijn,
We initially identified the error through an exception thrown by the TQuery
component in Delphi. We subsequently started IB console and verified the
presence of the indexes on the database in IBConsole.exe.
We were not specifically working within a transaction context. The actual
table drop and recreate were done through a TQuery component in a Delphi
application. The table we were creating was an archive table that combined
several other tables. The application was, through a TQuery component to
check to see if the table still existed, and if it did, to drop it and
recreate it and the indexes associated with it. The same application runs
as intended under IB5.6.
BTW (even though I don't think this matters, I'll include it for
completeness' sake), the app was running on a 2x1.33 Ghz P3 machine with
Win2K Server as the OS.
Thanks again, Martijn!
Brian
We initially identified the error through an exception thrown by the TQuery
component in Delphi. We subsequently started IB console and verified the
presence of the indexes on the database in IBConsole.exe.
We were not specifically working within a transaction context. The actual
table drop and recreate were done through a TQuery component in a Delphi
application. The table we were creating was an archive table that combined
several other tables. The application was, through a TQuery component to
check to see if the table still existed, and if it did, to drop it and
recreate it and the indexes associated with it. The same application runs
as intended under IB5.6.
BTW (even though I don't think this matters, I'll include it for
completeness' sake), the app was running on a 2x1.33 Ghz P3 machine with
Win2K Server as the OS.
Thanks again, Martijn!
Brian
----- Original Message -----
From: Martijn Tonies
To: ib-support@yahoogroups.com
Sent: Wednesday, January 29, 2003 12:02 PM
Subject: Re: [ib-support] Dropping tables and indexes in IB7
Hi Brian,
How did you check? Did you COMMIT your changes?
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
> We're in the process of trying to migrate from IB 5.6 to IB 7.0, and, in
> testing today, we identified a behaviour that seems... weird.
>
> Assume you have a table defined as follows:
>
> CREATE TABLE FOO (
> FOO_ID INTEGER,
> FOO_NAME VARCHAR(10)
> )
>
> CREATE ASCENDING UNIQUE INDEX FOO1 ON FOO(FOO_ID, FOO_NAME)
>
> Now, it has been our experience in IB 5.6 that entering the command:
>
> DROP TABLE FOO
>
> will drop not only the table, but also all of the indexes associated with
> this table. In our testing with IB 7.0, this does not seem to be the
case:
> we dropped table FOO, but index FOO1 was still present after dropping the
> table.
>
> So, is this a bug, a feature, or are we misreading how things are supposed
> to work?
>
> Thanks in advance for any assistance,
>
> Brian
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.