i recommend changing that code to the more backward compatible:use constant {DBX_CURSOR_RANDOM => 0, DBX_CURSOR_FORWARD => 1};
The second item is your use of AUTOLOAD in DBX.pm. Always define a DESTROY subroutine, even if it is empty and does nothing. When a DBX object is 'terminated', AUTOLOAD will be needlessly called.use constant DBX_CURSOR_RANDOM => 0; use constant DBX_CURSOR_FORWARD => 1;
Finally, while i certainly do not mind this module being available, i probably won't be using it for the same reasons that rdfield, Tomte, and Aristotle mentioned. If i want another abstraction, i use Class::DBI. Someday i hope that Pixie will make it's way into my production code (i think).
One reason i probably won't use your module is because i really can't stand record pointer style interfaces, they remind me too much of my SQL Server 7 days. >PDBI's selectall_arrayref and selectcol_arrayref have been more than enough for me to get database work done. Most of the time i just ship the resulting datastructures over to HTML::Template without even knowing what the field names are.
Thanks for contributing though, i for one appreciate it. :)jeffa
L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)
In reply to (jeffa) Re: DBX offers simplified access to the DBI
by jeffa
in thread DBX offers simplified access to the DBI
by batkins
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |