I think this should go in Meditations as well, since all the other sections can pretty much be ruled out. I have read the article and found the information in it to be useful.
I have just a few suggestions/questions which I will list below. (Keep in mind that I do not consider myself an expert, but that probably makes me a pretty good approximation of an average reader)
- Say I am writing a large perl/oracle application that needs to run on perl/mysql later. I am using DBI now. Should I really invest the time to learn DBIx, and why? It seems like the answer is yes, but it would be nice to have a paragraph that specifically addresses this kind of issue, pros and cons of switching to DBIx from good ol' DBI.
- Are there any performance issues of DBIx that I should be aware of?
- A world without SQL seems too good to be true. Is it?
e-mail neshura | [reply] |
I read the article as well, but while I found the artcile itself to be good, I disagree with the DBIx concept. Writting DBI without SQL has to be the same feel as driving a Porsche with auto-transmission. I like SQL and enjoy having absolute control over every little detail, but then again, that's my bad. :)
It seems to be that DBIx is (yet another) layer between the application and the database. The concept seems to interesting at first, but once you stop and think of it, whats the point really? Getting you to do you're work faster? More portability? Those can be acheived by knowing your tools better and finding a least common denominator.
That's what I do with SQL (and HTML). I have the exact oposite setup that you do. I'm writing SQL for MySQL and porting it to Oracle later on. Finding the least commong denominator between the both isn't that hard. I just run a Find/Replace on varchar, enum, int, and fields of the sort and then go through manually and find whatever needs special attention. I find that to be more practical, safer, and it usually on takes an extra 15 minutes per database.
Just my usual R$0.02...
#!/home/bbq/bin/perl
# Trust no1!
| [reply] |
i'm sorry, but i do not consider this a topic for "Perl
Monks Discussion".
here is the description of the purpose of this section
from the Site How To page:
This is where users can discuss features they
might like to see. Why the XP system kicks/sucks etc....
this is the place for site related issues.... not Perl
problems.
this topic is in no way "site related".
p.s. please don't provide URL's for us to visit without
making them hyperlinks. i might have read your article if it
had been linked (even though discussing it here is still
off-topic), but there's no way i will do so as it stands.
you presume too much of our willingness to labor selflessly
to your ends.
(i figure if i'm going to get voted down for being a
bitch in my explanation, i may as well explain all my
grievances at once.) | [reply] |
Not to mention that this is a re-post from "Please review my article". I don't understand what good it does to post the same requests several times. If we didn't comment on it the 1st time around, its not likely that we'll do it the second, third or fourth. This can become very annoying.
BTW: I'd post it to Meditations.
#!/home/bbq/bin/perl
# Trust no1!
| [reply] |
| [reply] |
