[TYPO3] Does the 1-2-3 install tool use DBAL?

[Daniel Smedegaard Buus]

Uros Kositer wrote:
> Daniel Smedegaard Buus wrote:
>
> Hi!
>
> I think this is reported in bugtracker 
> (http://bugs.typo3.org/view.php?id=4212)
>
>   
That definitely looks like the same deal! Only, "For the reporter: The 
quick fix is to revert this change." -- how would I do that?

Thanks, and thanks for the swift reply,
Daniel :)

> Regards
> Urosh
>
>
>   
>> Hey there...
>>
>> Still struggling with this IIS/MSSQL/TYPO3 setup. I got most working I 
>> think, but doing "Compare" in the 1-2-3 install tool and trying to 
>> create the missing tables results in this error screen:
>>
>> *Warning*: Variable passed to each() is not an array or object in 
>> *c:\Inetpub\wwwroot\t3t\typo3\sysext\dbal\class.ux_t3lib_db.php* on line 
>> *1660*
>>
>> *Warning*: Variable passed to each() is not an array or object in 
>> *c:\Inetpub\wwwroot\t3t\typo3\sysext\dbal\class.ux_t3lib_db.php* on line 
>> *1660*
>> ERROR: Query could not be parsed: "SQL engine parse ERROR: No ) 
>> parenthesis in list: near "(199)) ) "". Query: "CREATE TABLE 
>> sys_refindex ( hash varchar(32) NOT NULL default '', tablename 
>> varchar(40) NOT NULL default '', recuid int(11) NOT NULL default '0', 
>> field varchar(40) NOT NULL default '', flexpointer tinytext NOT NULL, 
>> softref_key varchar(30) NOT NULL default '', softref_id varchar(40) NOT 
>> NULL default '', sorting int(11) NOT NULL default '0', deleted int(11) 
>> NOT NULL default '0', ref_table varchar(40) NOT NULL default '', ref_uid 
>> int(11) NOT NULL default '0', ref_string varchar(200) NOT NULL default 
>> '', PRIMARY KEY (hash), KEY lookup_rec (tablename,recuid), KEY 
>> lookup_uid (ref_table,ref_uid), KEY lookup_string 
>> (ref_table,ref_string(199)) );"
>>
>> To me, all the CREATE statements look like I know them from working with 
>> MySQL. I would have expected them to look a bit different for MSSQL, 
>> knowing Microsoft's attitude towards standards. I'm thinking (read: 
>> fearing) that the install tool does not itself use the DBAL, meaning the 
>> installer is MySQL specific. Is this true? And, if so, how do I get it 
>> to install onto MSSQL?
>>
>> Thanks for any help you might offer,
>> Daniel Buus
>>     
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>
>