Jason Schulz wrote:
What happens when you use a third tool to query the data - does the data returned to it match Witango or the MySQL CC?

It's not clear from what you've written, but are you sure that MySQL CC is committing its transactions?
Yes, It's commiting the transactions... I just verified from a trace of the JDBC driver that Witango is setting autocommit = 0  Which is a perfectly logical explanation for the behaviour I'm seeing.

We'll see what Witango has to say...

/John

J.

On 24/03/2005, at 10:11 AM, John McGowan wrote:

I think I may have stumbled across a problem with Witango, JDBC and MySQL

I was hitting a page in my application listing the contents of a table and it wasn't listing everything, specifically it wasn't listing the record that i had just manually added via the MySQL Control Center. What I was able to determine was that it wasn't showing up because the JDBC connection was getting an Old snapshot of the data. Probably because Witango began a transaction, but never commited it, thereby causing the connection in the pool to have an Old view of the database.

I confirmed this by hitting the page again after hitting another taf file that had actual begin and end transaction actions in it. Now it shows the new data, but will not show newly added items. I have to go pickup dinner for my family so I haven't had a chance to make a very simple test case to reproduce, but I will, and I just was wondering if anybody else out there is using this type of configuration Witango 5, JDBC, MySQL.

/John


________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf



WITH IMAGINATION
Planning, Implementation and Management of Web Applications

160 Pacific Highway North Sydney NSW Australia 2060
phone + 612 9929 9229 fax + 612 9460 4770 
web - www.wi.com.au email - [EMAIL PROTECTED]


________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to