Pierre.....
I think you meant to refer to Trevor's libDB libraries here. Just in case someone gets confused.
I really agree with you about SQL being the perfect Rev sister ship, though, and I like the analogy.
One thing I've been thinking about a lot lately in conjunction with a set of apps I'm doing for my main client, is whether or not to use altSQlite out the gate for all data storage, skipping over cards and custom properties altogether (I'm talking about storage of record-type data here, not things for which cards and props are decidedly correct). One big advantage of that approach is that if the client's needs change and suddenly he wants the data on a networked server with a robust database, I don't have to change my code except for the connect stuff (typically one line) for it to just work. Since I seem to attract clients whose needs always change (I think that's why we call them "clients"), this has a lot of attraction for me. And now that altSQLite has overcome all the objections I had to Valentina (primarily the costs), this approach makes more and more sense to me.
Anyone else thinking along these lines?
On Apr 24, 2005, at 12:00 PM, Pierre Sahores wrote:
SQL is, probably, in about direct to disk datas storage and management, the perfect Rev sister-ship and, with the help of Chipp's libraries, a piece of cake to set-up. Leaen once how to drive SQL back-ends from within Rev and you will than use this winning combination all the time :-)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Shafer, Co-Chair RevConWest '05 June 17-18, 2005, Monterey, California http://www.altuit.com/webs/altuit/RevConWest
_______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
