Dear List,
we've got a question regarding running PHP with the MaxDB module
together with the unixODBC module.
Let me give you a little background on what we are trying to do:
At the moment we are trying to migrate the database accesses of a PHP
application from access via the ODBC interface(with call like
odbc_execute(...)) to access via the MaxDB interface(with call like
maxdb_stmt_execute(...)). For that purpose we set up a Apache 2 server
with PHP 4.2.2 and maxdb enabled running on a debian sarge box, which
works fine for the part of the application we have migrated already.
Unfortunately there are several parts of the application which can't be
easily migrated from ODBC access to MaxDB access. So for that parts of
the application we would prefer to keep on using the ODBC access variant
for some time, as this would make it possible to migrate those parts of
the application step by step.
And at that point we are running into trouble: We get the Apache/PHP
combination running perfect for unixODBC alone and same goes for the
MaxDB module alone, but with both modules enabled we get errors from the
unixODBC module which look like this:
SQL error: [nxDC[A G[ISLDS]SPD]Ual ocnett aasuc;42 O(), SQL state 0015
in SQLConnect
while the MaxDB module is working fine. As you can see the error message
looks quit messed up and, even worse, it only comes up on about 50% of
calls to the database(which luckily makes it more or less reproduceable
...).
We are aware that this could also be 100% unixODBC related, but as the
unixODBC alone runs extremely stable, this is also somehow tied to the
MaxDB module, we assume.
As we have experimented on this issue for quite a while without success
we hope that someone from this list has got an idea, or even better,
solved the problem before.
If you need more information on this, just let us know, any help is very
appreciated.
Best regards,
Mario Rutz
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
