[TYPO3-english] Oracle & Typo3 + TV

[Marek Bednar]

I'd like to say just my two cents.. As Jigal already mentioned, and agreeing
with him, we need to meet deadline. I am sure that my mother company will
try to contact the developers and will try to hire them for a bit, to make
Oracle run fine with desired exts, and will share it back to community.

But let me explain the (maybe a bit of) hypo regarding Oracle. Large
companies simply sometimes do not accept MySQL, since they are running
Oracle and they insist on it. If we want to meet their requirements and get
a job, we simply must try. I wonder myself as well, what are the future
plans of Typo3 development regarding its native or unnative database system.
I'd vote surely for such solution, that enables different SQL servers, with
an option to use specialities of particular SQL server as well. Such
solution though requires pretty smart db layering. Does typo3 team plan such
a thing?

regards,

Marek

2009/7/29 Jigal van Hemert <jigal at xs4all.nl>

>
> No offense meant to anyone, just trying to explain the not-so-ideal
> situations in real life...
>
> The same happens when you file a bug report in forge complete with a
> patch. It not exceptional that it takes several months for the issue to
> be resolved. I can't really blame the developer because (s)he also has
> to make a living, but it's not a practical solution to try to hire the
> developer to solve the problem.
> Most of the time the person/company who encounters the problem also has
> to meet a deadline. In the example of Oracle + TV, it means that the
> problem has to be solved before the normal site building can be started
> (otherwise you have to migrate the database also). This means that there
> are only a couple of days available (already extra time in the project)
> to solve the problem or alternative ways to build the site have to be
> found.
>
> Most people won't even try using Oracle after seeing the long list of
> problems. DBAL is a nice idea, but it isn't really a DataBase
> Abstraction Layer (it's more like a DataBase Compatibility Patching Layer).
> Trying to be compatible with a whole range of DBMSs on query level means
> that each DBMS is used in a suboptimal way. Hopefully this is a thing of
> the past with TYPO3 v5, but for the near future I can't really recommend
> anything other than MySQL for TYPO3.
> It is however pretty odd that TYPO3 officially supports a range of
> DBMSs, but core devs apparently don't have these available for the
> necessary positive votes from a core dev?
>
> Regards,
>
> --
> Jigal van Hemert.
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>