Humm, in lines of code and DB portability?
Graciliano M. P.
"Creativity is the expression of the liberty".
| [reply] |
Lines of code don't matter as long as I'm not writing them.
Portability? You can go all the way from SQLite through PostgreSQL through Oracle (we've done it) with Class::DBI. How much more portable do you want to be? Flat files? {grin}
I won't be interested in your project unless you can give me better reasons than that. In fact, I'd actively discourage you from inventing your own shiny wheel, while not contributing to Class::DBI if you feel something is missing there.
| [reply] |
From what I understand, Class::DBI needs a existing data-model to derive its classes from while HDB does not impose that constraint. At least, that was one of the constraints of Class::DBI when I looked at it, which has been a while ago.
-- JaWi
"A chicken is an egg's way of producing more eggs."
| [reply] |
Some Larry words:
- ...To not try to discourage people from trying variances. We do not want to stabelish one church, we want to stabelish many denominations...
Sincerely I have never used Class::DBI in a deep way, and I will be glad if you can show me how to do what I'm trying to do here with Class::DBI, and if I think that something is missing I will add to Class::DBI as I have added to other modules.
About lines of code, well, for me lines matters, specially for Perl, since we don't have a nice IDE with wizards like in Java were we really don't need to write things. Perl means write your own code.
And about the portability of Class::DBI, I can be wrong, but you are saying to me that DBI is portable over databases. Well, the SQL is not.
About my time, I'm paid to create components that help our development.
Graciliano M. P.
"Creativity is the expression of the liberty".
| [reply] |
