Subject Re: [firebird-support] Is it a feature or a bug of rows versioning?
Author Daniel Rail
Hi,

At February 23, 2004, 14:25, vmdd_tech wrote:

> I already reported this to
> firebird-odbc-devel@..., but
> I want to repost it here for second opinions.

> I know that Firebird has sophisticated versioning feature.
> But I am not sure the following is a feature or a bug of
> the ODBC driver.

> My application (it does not matter if this is a PowerBuilder or Java
> one)
> opens a Firebird ODBC connection. Since I want to implement
> transaction
> by myself, I turn off the autocommit flag.

> Then, my application will NOT be able to see any commited changes
> BY OTHER APPLICATIONS since I open
> the connection or since the last commit. For example,

> For simplicity, at time t0, my app issues
> select name from employee where id = 11
==>> "Original name"

> Then, at time time t100 (several minutes later), another external app
> issues
> update employee set name = 'New name' where id = 11;
> commit;

> Then, at time t200 (several minutes later), my app issues
> select name from employee where id = 11
==>> "Original name"


> Why did my app NOT see the "New name"?

What type of transaction isolation are you using(ReadCommitted,
Concurrency or Consistency)? Also, what happens if you commit your
first select, then start another transaction for your second select?
One thing you have to keep in mind is that even selects use
transactions.

--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)