[TYPO3-dev] Problem with long strings in tt_content (Oracle)

[Malte Jansen]

Moreno Feltscher schrieb:
>> It seems that Mysql's mediumtext gets mapped to varchar2(4000), but that
>> shouldn't happen because the former can hold much more data.
> Yes, that's true. LONG would be a possible solution, but I don't know
> what happens if i change this.. Therefore it would be nice, if there
> is anyone who tried this already. Otherwise I will test it on my
> testing-system.
> 
>>> Karsten, it would also be nice to hear something from your side about
>>> this. In the past we had a lot of problems with DBAL and Oracle, but
>>> no solutions for them.
>> No "official" solutions or none at all. How do you fare with Oracle currently?
> All the open bug reports are non-answered... I don't think this is a
> positive point to all the people thinking about implementing TYPO3
> with Oracle..
I think the problem is, that you have to pay for oracle. So most devs 
are only using MySQL, because it's free. So nobody can really check it.

> At all my system runs quite well, I have some problems with extensions
> which don't use the TYPO3 database syntax but I fix them manually.
> If I can solve this problem with the long strings quickly I will be
> able to set my system to a live-state in about a week.
> 
> 
> Moreno

You could make a small extension which is walking through $TCA and 
checks, which datatype is used, if it's to small, you can alter it. ;)

Cheers,

Malte