Subject | Re: [Firebird-general] Re: Wikipedia down due to MySQL problems... |
---|---|
Author | Lester Caine |
Post date | 2004-06-09T09:02:41Z |
Martijn Tonies wrote:
Both TikiWiki and TikiPro have Firebird 1.5 ports, but I'm working with
the TikiPro people to produce a good base with any reliance on a MySQL
original removed. Most of the MySQL 'features' have been bypassed over
time, and things like 'search' are now managed in proper tables rather
then using the MySQL FULLTEXT bodge. The result is that reliance on a
particular character set has also been eliminated, and changes of
language are easy - even where MySQL ENUM fields were used originally.
The next step is to replace some of the application code with triggers
to speed things up even more, but that does mean a lock in to a
particular engine. At present all the code will still work with any
ADOdb listed database.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
>>>>So, and only assuming that it is a problem solely of MySQL,If it doesn't then it should be black listed ;)
>>>>the Wikipedia project would need a volunteer to port to
>>>>a DBMS better fitting the ever growing load. Whatever the best
>>>>DBMS would be.
>>>
>>>And you think Firebird would be better?
>>>
>>>Do take in account that it fully needs to support unicode
>>>charactersets and all, something I believe you know quite
>>>something about :-)
>>>
>>>Etc etc... It might be a bit harder then you think :-)
>>
>>..Or not...
>>http://jaybirdwiki.firebirdsql.org/JayBirdHome
>
> I don't see any of the JayBird wiki in Chinese :-)
>
> Nevertheless, does this run on Fb?
Both TikiWiki and TikiPro have Firebird 1.5 ports, but I'm working with
the TikiPro people to produce a good base with any reliance on a MySQL
original removed. Most of the MySQL 'features' have been bypassed over
time, and things like 'search' are now managed in proper tables rather
then using the MySQL FULLTEXT bodge. The result is that reliance on a
particular character set has also been eliminated, and changes of
language are easy - even where MySQL ENUM fields were used originally.
The next step is to replace some of the application code with triggers
to speed things up even more, but that does mean a lock in to a
particular engine. At present all the code will still work with any
ADOdb listed database.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services