Basically, what do you think of the design? Of using text files vs. XML vs. a db?
And imp, as for you, young man, I normally would probably take advantage of the postgres server that we have here, but a) admin is controlled by someone else and b) it introduces another dependency. The sql box doesn't have a great history of reliability or response to customer queries (get it? queries? huhuhuhuhuh). If this were for day-to-day use, yeah, I'd probably use a db. But files are just as easy to me now that I've used Text::CSV::Simple a few times and it's one less dependency on an externality when the proverbial excrement hits the fan. I guess delevopment time also factors in.
_________________________________________________________________________________
I like computer programming because it's like Legos for the mind.
| [reply] |
Basically, what do you think of the design? Of using text files vs. XML vs. a db?
Wrap it all up behind DBI as a general interface layer and you'll be able to trivially (just change the DSN) switch between them ... so, for example, you can start with text files because they're easy to create .. or start with the db and if there're admin issues, switch to text or xml..
See DBD::CSV, DBD::AnyData, DBD::Pg, etc ..
(additionally consider putting Class::DBI or DBIx::Class or some other db abstraction layer on top of DBI)
| [reply] |
| [reply] |