Thanks for your information. By looking at these problems, I am not sure whether Perl with MySQL is a right way to go. By looking at the commands available, I thought I can use Perl with MySQL in Linux environment. If users have problems using them, I may have to look for other avenues. I still want to dig little further before moving away.
The application I am thinking about involves more data extraction and writing. I am not worried about reporting side, because reports are not a huge part of it. If someone has any experience, I meant positive experience using Perl in this type of an environment, please share your experience with me.
| [reply] |
By looking at these problems, I am not sure whether Perl with MySQL is a right way to go.
Do not misinterpret the above discussion as there being "problems" with Perl and MySQL. Nobody said there were problems with Perl and MySQL. The two work perfectly well together. The argument you see above is about using ORM's (e.g. DBIx::Class, Rose::DB::Object) which is an entirely separate issue which sparks arguments/debates/discussions like the one above. Start with Perl, DBI, and SQL, then maybe start looking at ORM's if you feel like it, try'em out, and use them if you feel that they're right for you.
| [reply] |
No. I am not going to come to conclusions immediately without testing on my own. I already installed Fedora and MySQL so far during my free time. I am going to install Perl and test it.
Thanks for your help. I will post my results in few days.
| [reply] |
| [reply] |
It is defintely the right way to go. As the above post says, ignore our discussion about DBIC vs bare-bones DBI and just take a look at the many examples for Perl/database interactions on the web. If you know SQL, you will find that Perl DBI will simply give you a way of issuing those SQL queries from within a Perl script and capturing the results for further processing, which is what you need. It may sound more tricky than it actually is.
| [reply] |