[TYPO3-dev] [DBAL] Problems with Postgresql and extension SQL files
Sebastian Roth
sebastian.roth at gmail.com
Sat Dec 30 01:10:55 CET 2006
Hi Masi,
On 2006-12-29 20:28:43 +0100, Martin Kutschker
<martin.t.kutschker at n0spam.blackbox.net> said:
>> INSERT INTO products (product_no, name, price) VALUES
>> (1, 'Cheese', 9.99),
>> (2, 'Bread', 1.99),
>> (3, 'Milk', 2.99);
>>
>> Using this syntax we would even save some bytes in the sql files.
>>
>> What's your opionion, how can we fix this?
>
> Always use full and only ANSI-SQL-compatible INSERT syntax. The short
> syntax will also break if you add columns.
>
> The installer/EM should issue a warning when it encounters the short syntax.
Alright, being close to the standard in shipped files is ok for me. The
jobs done when installing extensions do not require high performance
operations most of the time, too. I say this because db systems like
mysql/pgsql/oracle support some kind of COPY operation which performs
very well on this stuff.
So, i'd convert the sql files in static_info_tables for now.
Anything more to add?
Regards from 23c3,
Sebastian
More information about the TYPO3-dev
mailing list