It's trivial to write such a daemon using DBI:CSV. I've used such a daemon in some apps of mine.
Problem is that DBI:CSV doesn't support a full ANSI SQL syntax (no joins etc.) so any effort in
this direction should start with spiceing up DBI:CSV.
/t0mas
| [reply] |
While I agree the spicing the CSV driver might be a good starting point, one still has to remeber that just a plain CSV file won't cut it for a few issues. Namely:
- filesystem performance
- datatype support (longs, lobs, raws, etc)
- field constraints
- table constraints
- roles and permissions
- common objects (databases, tablespaces, etc)
- client server support
I guess what I'm getting at is: wouldn't an entirely new data format be needed to support all of the above features, or could these be acheived in some mischeivious (spellchecker needed) "linking-globing-OS glueing" kinda way?
This question has definitly become a meditation...
| [reply] |
BTW: I'm not sure this should be here or in Meditations, but since it IS a question....
#!/home/bbq/bin/perl
# Trust no1!
| [reply] |