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

[ries van Twisk]

On Dec 6, 2007, at 8:48 AM, Dmitry Dulepov [typo3] wrote:

> ries van Twisk wrote:
>> TYPO3 has a long history for not easily accepting bug and changes
>> for the core, I think bug track is a proof of that. This is  
>> changing now
>> because the core list is open, this is a good thing and me following
>> typo3-core
>> can see quite a big improvement there, well done.
>
> It is easy to say when you are outside. When you are inside and have  
> to choose whether to fix a bug or to do anything for customer (for  
> money), guess what you will choose.

I think I made a good comment there..... Hmmmm
However you must agree that TYPO3 core development is improving, right?

>
>
>> Because TYPO3 never created a strong DB API and try to be vendor
>> transparent people running a DB other then MySQL will keep on having
>> problems with extensions. TYPO3 core seems to be quite ok
>> (me checking that on PostgreSQL) but quite some extensions still
>> using MySQL syntax and often it's really hard to get in contact with
>> extension developers to get something changed.
>
> Well, that's not really core's fault :)

No,

First, I need to be absolutly clear to you: That is NOT YOUR fault,  
NOT TYPO3's fault.

but as you properly will understand and all the readers aswell is that
if you want to use any extensions, you have to face it's MySQL  
specific problems.
if an extension owner is going to update it's extension, and he  
doesn't communicate,
then you keep on patching your websites. Enterprise companies don't  
like that,
I am sure you will understand.


I hope I made myself clear, other whise let me know....


Ries