On Fri, Nov 12, 2010 at 5:50 AM, BareFeetWare <list....@barefeetware.com> wrote: > IMO, if you're implementing database logic (ie constraints and triggers) in > application code, then you're reinventing the wheel, making your package > unnecessarily complex and grossly inefficient. If you're just using SQLite > to store your data but doing all the logic outside of SQLite, then you might > as well just be saving your data to a CSV file or XML. See my previous > post for reasoning behind this.
>From http://www.sqlite.org/about.html : > Think of SQLite not as a replacement for Oracle but as a replacement > for fopen() So, yes, you might as well just be saving your data to a CSV or XML file. And I'm sure if you had a package to do that, someone would be arguing about whether your XML should allow for embedded transforms. -scott _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
