HMGforum.com

MySql and AdoDb experience

Re: MySql and AdoDb experience

Posted: Wed Oct 07, 2009 9:00 pm

by l3whmg

Hello everyone,
I understand your point of view on ODBC, which is a little more complicated (library, installing drivers) .
I really liked the "simplicity" of the syntax of the instructions that I could use, especially when I had to refer to individual fields or set up a SQL string and so on.
I believe that the library hbmysql creates fewer problems (I think using socket connection for access ), but I did not make significant evidence: I'll try!
About date fields (but the same for other fields) the problem is: can the language/compiler use them? I am limited to dates in the standard format (like dd-mm-yyyy) appropriately managed by clipper; as mentioned by Roberto, I've used a version of WAMP (http://www.appservnetwork.com). I'll try XAMPP (http://www.apachefriends.org)

Thank (many thanks) you for your attention shown to my little job.

Best regards.

Re: MySql and AdoDb experience

Posted: Thu Oct 08, 2009 7:50 am

by mol

I've tried MySQL and hbmysql for one reason - record locking future built in MySQL.
But, in my opinion, it doesn't work.

Re: MySql and AdoDb experience

Posted: Fri Oct 09, 2009 8:32 pm

by l3whmg

Ciao Marek,
I hope to indicate a right way. I remember having found these instructions:
- You must properly configure MySql, because it has the automatism that may affect or alter the use of Lock and Unlock even at the row level.
- It is better to use InnoDB because (it seems) is the only way (like Clipper) to perform the row-level locking.
- Best to approach the SQL string.
- Successfully set a parameter, when accessing to the database, which responds to precise rules (if you've noticed, in my library was provided a numeric parameter).