Hello All,
I have a rather peculiar situation with my Slide distribution. First, here's my
configuration:
Jakarta Slide 1.0.16
MySQL 3.23.49 with transaction support
mm.mysql-2.0.12 driver
Slide database is running on Solaris 8.
Slide application code is running on Windows 2000.
I developed a Slide client application that administers users in the Slide database.
The client adds slide users and modifies their passwords using the Slide Helpers. In
order for Slide to pick up any changes to the user properties, I turned off caching in
the source code (i.e. made AbstractServiceBase.cacheResults() return false).
Everything works fine if I have the slide database set up on MyISAM tables. In other
words, my client application adds a user or changes their password property, and the
SlideRealm picks up this change. However, when I port the slide database to InnoDB
tables, the SlideRealm doesn't pick up modifications to the user properties. I traced
the problem to the ResultSet returned in
JDBCDescriptorsStore.retrieveRevisionDescriptor(Uri uri, NodeRevisionNumber
revisionNumber):
statement = connection.prepareStatement
("select * from property where uri= ? and xnumber = ?");
statement.setString(1, uri.toString());
statement.setString(2, revisionNumber.toString());
res = statement.executeQuery();
This statement reports that the user password (for example) hasn't changed even though
I changed it with my client code and the mysql client shows that the password has in
fact been modified in the database.
I'm guessing that the PreparedStatement may be caching the results? Or perhaps
there's a problem with the MM driver. I upgraded to the mmy.mysql-2.0.14 driver but
the problem still persists. Does anyone have any ideas on this problem?
Thanks in advance,
Tom Keeney
Novus Consulting Group
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
