[Typo3-dev] Installing extention with sql... decimal(15,5)..
Georg Rehfeld
georg.rehfeld at gmx.de
Mon Feb 14 03:28:35 CET 2005
Hi,
Karsten Dambekalns wrote:
>>How about dumping current Mysql-specific SQL-code in favour of some
>>pseudo-SQL.
>
> Heh - why invent some abstracted language when you can have a subset of SQL?
> That is what we do now, we use plain SQL, but limit it to some extent.
> Remember, one (the) constraint when doing DBAL was to make it of almost
> zero impact to users running MySQL.
>
> And the problem Ries had was *not* caused by MySQL-specific code at all.
But please compare:
http://typo3.org/documentation/document-library/doc_core_cgl/TYPO3_specific_pract-1/
| - SQL: Use general field types in MySQL. Avoid all kinds of time/date
| fields which are specific to MySQL. For timestamps always use an
| integer and insert "UNIX-time". It's not humanreadable, but it will be
| portable the day we implement Database Abstraction.
and also:
http://typo3.org/documentation/document-library/doc_core_cgl/Supported_SQL/
whole page and specifically
| In TYPO3 we use a subset of MySQL compliant SQL as our "abstraction
| language". It means that the SQL is readily executed by MySQL while it
| may need translation if any other database is needed.
|
| To make sure your SQL is compliant with the TYPO3 SQL subset you can
| use the class t3lib_sqlparser to parse it.
|
| Generally, the SQL you can use in TYPO3 should be rather "simple".
| ...
Though I believe DECIMAL to be common enough to be allowed in the
future.
regards, Georg
--
___ ___
| + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg
|_|_\ |___ georg.rehfeld.nospam at gmx.de +49 (40) 23 53 27 10
More information about the TYPO3-dev
mailing list