About your problem for distribute your application, why not send it with the DBI & DBD modules in the binarys, since you are publishing binarys with PerlApp.
You can wait the module HDB to be published, that works with DBI. With HDB you don't need to use SQL, you just use the commands of the module and perl syntax (all the query syntax is based on Perl), and HDB convert to the SQL syntax for each database. In other words, all your commands in HDB will work with any database, and if you want to change the DB you don't need to change the commands of your script. For example, I develope my site with HDB, and I test it in my Win2k desktop, using HDB::SQLite, but when I send to the server it works with HDB::Mysql, the only thing that I change is in the HDB->new(type=>'sqlite'...) to HDB->new(type=>'mysql'...). HDB make all the convertions of types of columns, and resources that one DB have and others not. And the module is very easy to use, I have peoples using it a lot but doesn't know anything about SQL syntax!
Graciliano M. P.
"The creativity is the expression of the liberty".
In reply to Re: To DBI or not to DBI
by gmpassos
in thread To DBI or not to DBI
by rzward
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |