Re: [sqlite] Good books to lear SQL using SQLite?
On Mon, 30 Apr 2012 10:18:33 -0400 "Arbol One" <arbol...@programmer.net> wrote: > I am learning SQL using SQLite, can anyone tell me of a good book to > learn SQL using SQLite? I'm very happy with Owens' The Definitive Guide to SQLite...there is 2nd ed. now. Sincerely, Gour -- As a strong wind sweeps away a boat on the water, even one of the roaming senses on which the mind focuses can carry away a man's intelligence. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Best LINQ provider for SQLite?
On Fri, 9 Mar 2012 19:49:32 + Rob Richardson <rdrichard...@rad-con.com> wrote: > If there is a way to search the archives, could someone please show > me? http://dir.gmane.org/gmane.comp.db.sqlite.general Sincerely, Gour -- Whatever action a great man performs, common men follow. And whatever standards he sets by exemplary acts, all the world pursues. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] best way to use sqlite as application's format
On Wed, 22 Feb 2012 20:52:54 -0500 Richard Hipp <d...@sqlite.org> wrote: > Here <http://www.sqlite.org/cvstrac/wiki?p=UndoRedo> is a write-up > from 2005 in which I describe a technique I used to implement > unlimited-depth undo/redo in a application that used SQLite as its > file format. There was no "File/Save" button. But you could undo as > far back as you wanted - even in to prior sessions. Wonderful! Thank you very much for this reference. > That application was written in Tcl/Tk, but the idea works the same in > D or whatever language you want to use. OK. I hope we can continue asking here (despite using D) since there are no replies in D newsgroup where people are usually occupied replying to gigantic threads. :-) > Another approach is to record historical versions of rows in the > database somehow. In other words, design your schema as if it were a > Version Control System > <http://en.wikipedia.org/wiki/Revision_control> that keeps a > permanent record of past images of the data. Bonus points if you can > make it operate as a Distributed Version Control > System<http://en.wikipedia.org/wiki/Distributed_Version_Control_System>. Hmm, I must say it sounds intriguing although I'm not sure whether we really need it since once when we calculate the whole set of data for one 'person', it would not change much, iow. the data in the database are not so much prone to change as much we're interested to study/query relations between the data. > Note that Monotone <http://www.monotone.ca/> was a pioneer in the > DVCS space and their file format is an SQLite database. Note also > that SQLite itself is maintained using > Fossil<http://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki>which > is another DVCS that uses an SQLite database for storage. (Yes, the > source code for SQLite is stored in an SQLite database. Recursion is > a wonderful thing.) Heh...my VCS really started with the Darcs and I used Monotone for some time - too bad it was too slow for Linus so world ended up with Git itself. ;) I did use Fossil for some time (and still looking what's going on) - it's very fine piece of software, but to make our life simpler we ended up using Mercurial along with hg-git when the needs arises. Having more interoperability features in Fossil (e.g. 2-way sync with other DVCS) would make it even more appealing, although it's questionable how much is this in sync with Fossil's objectives. ;) > Or, you could do all your work inside a transaction and then > implement a File/Save button that does a COMMIT for you. That > approach is conceptually simpler from the point of view of the > programmer. But it is less intuitive to users. I agree. > And if your application crashes, you lose all of your work done since > the last File/Save. Considering data won't change much, it might be sufficient. > If you do use this approach, please note that SQLite does support > nested transaction<http://www.sqlite.org/lang_savepoint.html>which > might be useful to you. Thank you very much. I was also not aware of that one...it's final time to start using those two books about Sqlite which I have. :-/ Sincerely, Gour -- Thus the wise living entity's pure consciousness becomes covered by his eternal enemy in the form of lust, which is never satisfied and which burns like fire. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] best way to use sqlite as application's format
On Wed, 22 Feb 2012 23:04:55 +0100 Petite Abeille <petite.abei...@gmail.com> wrote: > Are you actually trying to solve a concrete problem? Yes. > Or creating one out of thin air instead? No. > http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer+Science.aspx Thank you. It seems we are heading towards 'solution' 1) along with 5) by replacing using OOP in D with FP. Sincerely, Gour -- But for one who takes pleasure in the self, whose human life is one of self-realization, and who is satisfied in the self only, fully satiated — for him there is no duty. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] best way to use sqlite as application's format
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 22 Feb 2012 17:10:39 -0800 Roger Binns <rogerb-jfdgoz7s+bwwqnjq7v0...@public.gmane.org> wrote: > Just start using SQLite and see what happens. Good one. We'll try to (artificially) populate our sqlite database and then play with it. > You don't have to use an ORM. And if you don't use one, you'll > eventually see if you need one and what functionality it needs. After reading The Vietnam of Computer Science it definitely looks to me that using OOP costs too much for not much gain and we'll try to produce more FP-oriented code. > I do have two other recommendations. The first is to ensure you have > a sensible way of testing. A layer between your code and the > database may make that easier or harder - validate up front that it > will be the former. I believe one layer less is better in our case. :-) > The second is to ensure you have an undo mechanism, as this will > affect your schema and triggers. One thing I worked on didn't even > have a 'save' menu item. Every action you did resulted in a database > change. You could easily undo these. You could also see of the > objects as they were at any prior point in time, being able to undo > or redo any change. That sounds great, although atm I'm not sure how to tackle it, although it seems that Richard is giving some nice advice in regard. Sincerely, Gour - -- What is night for all beings is the time of awakening for the self-controlled; and the time of awakening for all beings is night for the introspective sage. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJPRh/jAAoJELhxXPVStcgQKGsP/A0Zqn9bU+AK8mr09YF3jCKf bkAvsiyl2cZt28Lr8oDuuowwdF3w561+RsV8pUAZ9dg4Y0zBtVF/vz5ZeVlh3CRD KpD2T94iR6jyuTgrGV4t/JPH+F+e3BQ3G62T/r7WElbPClZqHUkqsXaS/2jbnB0T UaoYqd2az24vIRCgQXpXwTOtF71zMItcb6NN2kGtyRdS7uVROHHqk4hxbcN2BP6Y ObqHjplq5t2q18APaoQuTWmpVxv3C1XK/FIwBDpsmBRjwPR2wY+z+yPXXo9ekD13 18qc4rbw9rGLTtVl0gV73dapiZ9d7goN/V/gt+oUTcc7G7/dj+p3xfYJvMNewheh YrnUUVShA7d/OoTT4dQin9Cka+RTBnJuSQP8BCARFtgpWPTcDZ/l43sEWTQXDBES UDRq5Mr7r2x28NmZQtR4X7kOPjARbAz73v1Bf35EWsT4Sf1QDWY+HHj0wTY8SNfz tpVd6Gn3jyac2AqZ/N/JDRYsxg3CqLtSIBxQWST/0s6tWtOtx7DYAFM4o72d/GQe cUQOT59g5Ltf/qGJ2WJywB0DZ33w32ZkvIyXJNSZ7Fvy+r068hoC4iR5SQ846N7J f1WK4JGa+u3tCnFCMwp2RHitrYmALevQE5Wc+X0VwFrAUaV247STnMhqU9t6Hte5 ipQVBxtBSz8AXa/d9HIF =W+90 -END PGP SIGNATURE- ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] best way to use sqlite as application's format
Hello! We're considering what would be the optimal way way to resolve "object-relational impedance mismatch" problem in our application which we would like to write using D language. Considering it's planned to be multi-platform desktop GUI app and have extensive research capabilities available for learning & studying purposes - it means to be able to put queries against the whole database of available data - we are thinking that using embedded database - sqlite3 - as application's natural storage format would be a nice fit. Sqlite3 offers robust format available for multiple platforms. Moreover, having RDBMS could greatly simplify the code handling all kinds of queries againsta the data which would be required to write otherwise. Otoh, here we come to the well-known "object-relational impedance mismatch" problem and wonder how to resolve it, iow.: a) we are not aware of any ORM available for D, so using relational data model + D with its OOP paradigm, means to resolve the mismatch by hand by writing required ORM b) use relational model "as it is", leave OOP (in D) behind, but we wonder whether such approach makes sense in the language which is higher-level than C. (E.g. Fossil SCM written in C uses sqlite3 as storage format.) c) several papers/posts which we read before and recently (like "Functional-Relational Impedance Match" Eric Meijer's The Confessions of a Used Programming Language Salesman) tend to suggest that using relational data model goes better with FP languages or that the latters can overcome the above mismatch problem better, which would lead to putting D's FP capabilites to extreme or d) something else? Sincerely, Gour -- The embodied soul may be restricted from sense enjoyment, though the taste for sense objects remains. But, ceasing such engagements by experiencing a higher taste, he is fixed in consciousness. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
