🚀 go-pugleaf

"David Bakhash" <cadet@alum.mit.edu> wrote in message
news:m31yq4qb58.fsf@alum.mit.edu...
> >>>>> "hb" == hiram barber <hiram.barber@home.com> writes:
>
>  hb> While using isql (either command line or through IBConsole) to
>  hb> retrieve a row count (select count(*) from <tablename>) on an
>  hb> InterBase database it returns grossly inaccurate numbers
>  hb> (i.e. 129 for a table with a couple of thousand rows).
>
> While I don't think that this is the problem, I will throw it out
> there, because it's bit me a time or two.
>
> IB has a certain default isolation level that makes it appear to
> return wrong data.  Make sure that you've committed all other pending
> transactions from other windows, applications, etc.  Close them, then
> restart isql, and then do your select count(*).  See if that coincides
> with the number of rows that get printed to the console when you do a
> select *.  If you still see the problem, then yes, it's a bug.  But
> right now, it's still very possible that you *think* that the database
> contains these thousands of rows while they havn't been committed in
> the snapshot that your isql program is running in.  Also, note that
> even if they *were* committed, isql might still be in an old
> snapshot.  I don't know the details, except that you really must
> commit in all applications, close them, then restart isql and check
> again.
>
> dave

I appreciate your feedback.  I have been able to reproduce this on linux
and solaris platforms, windows works fine.

I have a feeling that the data is never being written to disk properly, but
continues
to queue (within interclient/interserver? memory?).  We open a database
connection pool, insert
via Auto Commit, but have someother isolation levels.  I currently have
Borland support
working on this to try to figure out what is going on.  But is something
that readers
of this group might want to keep a close eye on if they intend to use
InterClient JDBC.  It
seems like a concurrency issue between JDBC vs. other (ODBC, BDE, iSQL,
etc.).

Meanwhile, does anyone have JDBC code or specific database settings where
they are
manipulating the transactions and isolation levels?  Anything is worth a
try, please don't
be shy!

Regards,
Hiram