what do you miss? dBase syntax? dBase IV had already a built-in castrated implementation of SQL. There was no nested queries, as in MySQL. As a matter of fact, MySQL' features, design and restrictions are very close do dBase/FoxPro.
Perl is an excellent tool for CGI programming and other similar tasks where the system vastes a lot of time to communicate with some SQL server or open/close files.
But using Perl engine to create slow-and-dirty drivers... Don't think it's a good idea.
Slashdot Mirror
what do you miss? dBase syntax? dBase IV had already a built-in castrated implementation of SQL. There was no nested queries, as in MySQL. As a matter of fact, MySQL' features, design and restrictions are very close do dBase/FoxPro.
So, you have all you want.
Perl is an excellent tool for CGI programming and other similar tasks where the system vastes a lot of time to communicate with some SQL server or open/close files.
But using Perl engine to create slow-and-dirty drivers... Don't think it's a good idea.