[TYPO3-dev] PostgreSQL native drive for TYPO3 status update... andquestion about : 102: These fields are not properly

[ries van Twisk]

Hey Steffen,

> your tries opens the question why not supporting native DB-classes.
> Ok, all can be done with DBAL, but this decreases the performance.
Agreed...

> In my eyes t3lib_db has to be a wrapper class, the native actions  
> should be
> in the native subclass as mysql, PG , oracle etc.

this is exactly what I am currently doing.
However, I needed to make an XLASS over t3lib_db.
That basically means that we now have a native interface for PostgreSQL.

I quickly did some performance testing and that showed me that the  
performance
is around the same in comparison to MySQL native version.

good news for that...


Ries


On Sep 30, 2007, at 4:24 AM, Steffen Kamper wrote:

> Hi ries,
>
> your tries opens the question why not supporting native DB-classes.
> Ok, all can be done with DBAL, but this decreases the performance.
>
> In my eyes t3lib_db has to be a wrapper class, the native actions  
> should be
> in the native subclass as mysql, PG , oracle etc.
>
> vg  Steffen
>
> "ries van Twisk" <typo3 at rvt.dds.nl> schrieb im Newsbeitrag
> news:mailman.844.1191086662.1851.typo3-dev at lists.netfielders.de...
>> Hey Guys,
>>
>>
>> yesterday and today I had some time and ideas to work on a native
>> PostgreSQL driver for TYPO3.
>>
>>
>> Current status is:
>>
>> 1) Using a TYPO3 backend module you can transfer a MySQL database to
>> PostgreSQL both Schema and data. It's quite crude and needs to get
>> cleaned up a bit.
>> 2) using a xlass method I replace TYPO3_DB with a postgresql version.
>>
>> That means initial load needs to be done with MySQL, but then any   
>> site
>> can be transfered to postgresql...
>>
>> Core FE and BE works, however when I insert a content record I  
>> get  this
>> message:
>>
>> 102: These fields are not properly updated in database:
>> (CType,sectionIndex) Probably value mismatch with fieldtype.
>>
>> When I compare all fields in PostgreSQL and MySQL they are  
>> exactly  the
>> same, yet TYPO3 complains.
>>
>> How does typo3 does this comparison and where in core can I check  
>> for  the
>> evaluation of these fields?
>>
>>
>> One other problem I have is caching.. sometimes TYPO3 returns an   
>> empty
>> page, sometimes not.
>> I also had caching problems with MySQL (teh duplicate entry bla  
>> bla  bla
>> issue) so I don't think it's a PG problem,
>> but more like a TYPO3 problem. Not sure where yet...
>>
>> thanks,
>> Ries vanTwisk
>>
>>
>>
>>
>> --
>> Ries van Twisk
>> Freelance TYPO3 Developer
>> email: ries at vantwisk.nl
>> web:   http://www.rvantwisk.nl/
>> skype: callto://r.vantwisk
>> Phone: + 1 810-476-4193
>>
>>
>>
>>
>>
>>
>
>
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

--
Ries van Twisk
Freelance TYPO3 Developer
email: ries at vantwisk.nl
web:   http://www.rvantwisk.nl/
skype: callto://r.vantwisk
Phone: + 1 810-476-4193