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

[ries van Twisk]

Alright,

wrong decision about the upper/lower case issue..

I just wanted to prevent some additional DB overhead to
make that DB returns fields in the right case.

Ries


> Hey Ingmar,
>
> I currently solved the problem with tan xlass on tce_mean like this :
>
> ......
> 				foreach($fieldArray as $key => $value)	{
> 					if ($this->checkStoredRecords_loose && !$value && !$row[$key])	{
> 						// Nothing...
> 					} elseif (strcmp($value,$row[strtolower($key)]))	{
> 						$errorString[] = $key;
> 					}
> 				}
> ......
>
>
> Since my DB migration tool migrates al fields regardless of case to
> lowercase in PostgreSQL
> and while TYPO3 uses a mix of lower/upper case the strcmp line will  
> fail
> when data is compared from given to what is returned by the DB.
>
> The $row arra might contain:
>
> ctype => 'text
>
> while the array given by type contains
>
> CType => 'text
>
>
> When I lowercase the key, then I can always find the correct value in
> the DB.
>
> By adding an uppercase CType in PostgreSQL will create an other  
> array of
> problems and is possible less compatible with extensions. I might
> want to revert
> to that solution incase this one give me more problem.
>
> However BE runs smoothly now in PG:..
>
> Ries
>
> On Sep 29, 2007, at 1:32 PM, Ingmar Schlecht wrote:
>
>> Hi Ries,
>>
>> here you go:
>> http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/browser/typo3/
>> TYPO3core/branches/TYPO3_4-1/t3lib/class.t3lib_tcemain.php?
>> rev=7069#L4919
>>
>> cheers
>> Ingmar
>>
>> ries van Twisk schrieb:
>>> 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
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> -- 
>> Ingmar Schlecht
>> TYPO3 Association Active Member
>> _______________________________________________
>> 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
>
>
>
>
>
>
> _______________________________________________
> 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