The problem is the different way that MySql and MS SQL use connection handles. Some databases (MySql included I believe) allow for multiple activities on a single connection handle. However, MS SQL (and probably Sybase as I believe it's the underlying connectivity library) only allow a single activity (such as on ongoing query) to occur on a single connection at a time.
Therefore, multiple connections, with probably identical connect information are required. DBI's cached connection code uses the connection information to identify handles. Thus, there is a problem.
nic
I see the problem now, my mistake, I incorrectly thought he was talking about MySQL that being the commonly used database that does not support subselects (apparently he is developing on SQL Server and the final product has to run with DB/2. via the DBD:ODBC).
- MS SQL does support subselects (I have never used DB/2) - so you should be able to do pretty much anything in a single (big) SQL query, but I guess you know that.
So what caused the other problems he mentioned with his JOINS, they seemed perfectly correct to me (in theory), hence I assumed he has an error in his actual SQL or a name conflict.
Always useful to know these little things :-)
Simon
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.495 / Virus Database: 294 - Release Date: 30/06/2003
