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

ries van Twisk typo3 at rvt.dds.nl
Tue Oct 2 15:41:22 CEST 2007


Hey Moreno,

At the current stage no unless you are willing to change some code..
Since to migration tool doesn't have a UI yet. However this is easy  
to add.

it has only been quickly tested at core at the current stage, no  
extensions
what so ever... just an Hello World on the screen with a default  
template.
I also have seen a couple of small 'bugs' in the BE, but they are no  
roadblock,
that means adding content elements and RTE works fine.

it would be nice if we can combine forces and make a Mysql -> PG and  
a MySQL -> Oracle
migration tool from the typo3's BE. This should be easy to do if we  
do it quick and dirty..

Ries








On Oct 2, 2007, at 8:18 AM, Moreno Feltscher wrote:

> This would be great, yes!
>
> Is it possible to test your tool?
>
> Moreno
>
> On 10/2/07, ries van Twisk <typo3 at rvt.dds.nl> wrote:
>>
>> Hey Moreno,
>>
>> do you think we should write a native driver for oracle aswell??
>>
>> I think the tool I wrote to migrate an MySQL database to PostgreSQL,
>> will also work on Oracle. However I don't have any oracle  
>> experience..
>> The only difference I see between Oracle and PostgreSQL is that
>> empty strings are handles as NULL values. But I think
>> they are tricking that in TYPO3 core as I have seen from a couple of
>> queries.
>>
>> I am not planning to do it yet... but after I finished this proof of
>> concept...
>>
>> Ries
>>
>>
>>
>>
>> On Oct 2, 2007, at 3:12 AM, Moreno Feltscher wrote:
>>
>>> On 9/30/07, ries van Twisk <typo3 at rvt.dds.nl> wrote:
>>>> I am currently curious how other people solve this issues when  
>>>> using
>>>> other databases,
>>>> I know there are some that uses oracle, and some that uses  
>>>> PostgreSQL
>>>> and wonder how they bypass these problems. (I am not sure how DBAL
>>>> will handle this internally)
>>> You're right, I had exactly the same problem with Oracle 10g. The
>>> solution in my case was, to create all the tables with TYPO3's  
>>> install
>>> tool (not with the Oracle migration tool).
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> 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










More information about the TYPO3-dev mailing list