On Tue, Jun 24, 2008 at 4:53 PM, Aran aran@organicdesign.co.nz wrote:
For example the problems in the special pages DJ Bauch mentioned is due to the GROUP BY being part of a fully constructed SQL string rather than a DB::selectJoin method or something instead. The GROUP BY would then be part of an option array so it could be modified in the MSSQL implmentation of that method.
That might be best fixed where the queries are used, then. That syntax is rather opaque anyway.
Also another issue is that MSSQL doesn't like inserts on auto-increment rows which are declared as NOT NULL but then are inserted with NULL's. MySQL ignores the NULL since its an auto-increment row and so not actually inserted. But MSSQL doesn't like it so it may be good to change such NULL's to 0 or "" or whatever type is appropriate, or not include those columns at all in the inserts.
This is fixable at the abstraction layer, or should be. Look at what PostgreSQL does: they don't submit a NULL, they insert some function call or other.