Zeoslib Portal

Pitfiend,

You are right and wrong i think. The huge list of protocols can be confusing. But here we've to start from the premise that a "normal user" with lese expieriences does use Zeos. You, andrea.lai, Mark and other users do know that we can use MariaDB. But how to step such FAQ's ire this thread of Edson?

And our documentations are to weak! Long times looking for somebody who can help us here..

Michael

What I'm trying to mean, is that the protocols' list need to be simple. For example, in ZeosLib 6.x there are 5 entries for mysql: mysql, mysql-4.1, mysql-5, mysqld-4.1 and mysqld-5. Some other protocols has more entries.

What I suggest, is to have a simpliest list: mysql and mysqld, and then internally you load the most up to date library you have access to, no matter if it is mariadb or mysql, take in mind that the libraries have the same filename.

I think that a readme file can solve any trouble about what can or can't be done with ZeosLib, as well as what are the minimum needed libraries, maybe some website links could help. Leave the documentation monster for a later fight.

Pitfiend,

That's a good point! Yes this coup be equal solved by checking the versions(if that is supported) instead of an endless list of PlainDrivers. Next point is that this can thin out the Zeos-Code on the Plain-units. I'll think about this and asking the project-manager what he's thinking about your proposal.

Michae

you welcome. but the one that deserve the credit and our thanks is you, keep doing that excellent work.

EgonHugeist wrote:andrea.lai,

which protocol did you use for your stress tests? MySQL-5? Adding a new MySQL descendant PlainDriver and protocol name 'MariaDB' is no problem..

Michael

Is sufficient use normal mysql protocol.
I use MariDB 5.3.x version with Zeso 6.6.6 and Delphi7.

Bye

In my opinion, I find it interesting MariDB add the list of protocols supported, so users will know that also supports MariDB Zeos.

Edson