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

[ries van Twisk]

On Dec 6, 2007, at 8:15 AM, Ingmar Schlecht wrote:

> Hi Moreno,
>
> Moreno Feltscher wrote:
>>> 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.
>> There are many companies (for example mine, that's also the reason  
>> why
>> I have to solve all this problems) which use Oracle. If TYPO3 has
>> ambitions to be a professional CMS you need to keep this in mind..
>
> Then those big enterprises using Oracle should go and fix the bugs.
> They're invited to send their patches to the core list just like  
> anybody
> else:
> http://typo3.org/teams/core/core-mailinglist-rules/
>
> cheers
> Ingmar
>
> -- 
> Ingmar Schlecht
> TYPO3 Association Active Member

That's easy to say but...

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.


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.


Give it some time... it will come, certainly for TYPO3 version 5.


Ries


--
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