Re: DB_DataObject and MS SQL

To make this work, limit needs to store the proposed limit as an array when you call $do->limit(1,2); and then build the SQL statement in find(), and call alterLimitQuery on it rather than building the limit part of the query as limit() function at present, I've falling behind on merging in the changes need to Flexy, so this may not appear soon, unless someone sends in a patch.. Regards Alan Demian Turner wrote:

Hi Markus That's good news, thanks for the info. I'm guessing that the LIMIT issue is at the PEAR::DB level? It's a pretty important feature, will check if it's logged in bugs. cheers Demian Markus Wolff wrote:

Demian Turner wrote:

Hi Has anyone had any experience using the above combination? I have a contract coming up where there's the possibility to use DB_DataObject in a number of apps and am unable to test with MS SQL as I don't own a copy.

Hi Demian, I haven´t tested it excessively (yet!), but some quick tests have shown that DO seems to be MSSQL-compatible. Classes are being generated correctly from the datasource. Fetching data works as well. There seems to be an issue with LIMIT queries (SELECT TOP...) due to the fact that MSSQL doesn´t support a real equivalent to the LIMIT option. As far as you don´t need that, you should be fine. CU Markus