Hello
I am looking for reliable components to connect to MySQL from Delphi 7. I have tried the Scibit components, and found these (after two years) to be buggy, slow and with a lot of overhead.
I am currently looking at the components from CoreLab, MicroOlap and ofcourse at Zeos.
Can you please tell me what are the advantages/disadvantages of these components ?
Besides I have found these units written by Cristian Nicola at sourceforge
can anyone tell whether all the mentioned components, including Zeos, are based upon C. Nicolas implimentation ?
Kind regrads
Rozh
Components for MySQL/Delphi
Moderators: gto, cipto_kh, EgonHugeist
Hello!
I think that DirectSQL is a totally different project compared to Zeos. The basic idea is quite different (no DLLs,.. etc.). For other project I don't know.
I have tried many MySQL components and found many of them a very valid choice. To be honest, I never liked SciBit's components, because of their quite different aproach (many "strange" properties/methods). I tried MicroOlap too, but had a lot of problems with TDateTime fields at that time (but I think they fixet all the bugs). So here we came to Zeos...
I'm using Zeos for two main reasons. The first is that many servers are supported, so my applications are relatively easy portable (not only theoretically, but also practically). The second is that the project is opensource.
I like Zeos and I'm following the development from the beginning.
Speed is not an advantage of Zeos, for this is better to stick with SciBit. Not that the components are veeery slow, just they are not the fastest.
Hope it helps you to choose
I think that DirectSQL is a totally different project compared to Zeos. The basic idea is quite different (no DLLs,.. etc.). For other project I don't know.
I have tried many MySQL components and found many of them a very valid choice. To be honest, I never liked SciBit's components, because of their quite different aproach (many "strange" properties/methods). I tried MicroOlap too, but had a lot of problems with TDateTime fields at that time (but I think they fixet all the bugs). So here we came to Zeos...
I'm using Zeos for two main reasons. The first is that many servers are supported, so my applications are relatively easy portable (not only theoretically, but also practically). The second is that the project is opensource.
I like Zeos and I'm following the development from the beginning.
Speed is not an advantage of Zeos, for this is better to stick with SciBit. Not that the components are veeery slow, just they are not the fastest.
Hope it helps you to choose
Hello
Thank you for your reply. I do not need the portability feature. I am quite sure to stick to MySQL, so I will not implment Zeos due to the overhead that you describe. So thank you for this advice.
I still think that Zeos is a good initiative, and I am always a fan of OpenSource projects. I will start to implement CoreLabs components. Looking at the dokumentation makes one think that these are good components.
Thanks
Thank you for your reply. I do not need the portability feature. I am quite sure to stick to MySQL, so I will not implment Zeos due to the overhead that you describe. So thank you for this advice.
I still think that Zeos is a good initiative, and I am always a fan of OpenSource projects. I will start to implement CoreLabs components. Looking at the dokumentation makes one think that these are good components.
Thanks