This is an Informix question, not a Java question, you'd be better asking
on an Informix group.
> This is kinda wierd, i'm using an informix DB, i create an index using
> a
[quoted text clipped - 4 lines]
> been
> dropped, altered or renamed.
I suggest you may need a commit after the create index. However, having
said that, should you be creating an index? Is this installer code, or is
it application layer code, in which case why is the application making
structural changes to the database?
My general advice is to get database /structure/ right at install time,
normally by running a SQL script, and subsequently leave it alone as far
as possible.

Signature
simon@jasmine.org.uk (Simon Brooke) http://www.jasmine.org.uk/~simon/
Tony Blair's epitaph, #1: Tony Blair lies here.
Tony Blair's epitaph, #2: Trust me.
berso - 05 Oct 2006 16:44 GMT
Yes i think is more an informix q', what i'm doing is generating a
table that have to be refreshed every month, and the fastest way to
doit as far as i now is to drop the table , then
create the table with out indexes, insert the data, and then create the
indexes....but then i have to do a bunch of updates, and then is when
the problem starts, anyway i think it still related to java in some way
because, i wonder why the statement class returns the control to the
program if the index is not yet created, i'm agree with the commit, but
the DB is not transactional so i can't use it, i may just create the
table with indexes, or even just delete the data even if it takes a bit
longer....Thanks anyway.
Simon Brooke ha escrito:
> This is an Informix question, not a Java question, you'd be better asking
> on an Informix group.
[quoted text clipped - 22 lines]
> Tony Blair's epitaph, #1: Tony Blair lies here.
> Tony Blair's epitaph, #2: Trust me.