I can answer as I purchased sqlYoga and have tested dbLib. The former allows multiple database connections. It allows you to save those connections to a button (puts info into custom prop) and then load them as you need, or you can simply work with them in memory. You can create other objects as well. There are query objects, table objects, etc. and working with them is simply a matter of calling functions and commands that set or get the parameters of those objects.
dbLib works with one connection at a time. While you can save all the set conditions and restore them later, it is really designed to work with one database connection at a time, and one set of query parameters at a time. When you set conditions on an sqlYoga object, the conditions are persistent throughout multiple queries. dbLib however resets the conditions after each query. Frankly I find that approach a little odd, but it is workable, since you can save your conditions to an array. sqlYoga also has a lot of utility functions. For instance you can get the structure of a table with a simple function call, or get a list of tables in the database without knowing any SQL or the particular syntax for that flavor of SQL. Both do a fairly good job at insulating the developer from having to write his own queries, but complex queries like compound conditionals with mixed and's and or's however will have to be coded and both provide a way to pass complex queries. dbLib is much simpler to get started with. It doesn't bother about the connection itself. It expects you to handle that part. Once you do that, you pass the id to a function which stores it, and all calls after that are made with that id. sqlYoga requires that you create a database object, and then a connection object in memory at least before you can start working with your tables. sqlYoga has a bit of a learning curve to understand how to work with the custom "objects" that Trevor came up with. Once you get past that you begin to see the advantages of doing things that way. I have a method I use for accessing my database that is used throughout most of the app I am working on, but from time to time I find I need a quick query, and I don't want to have to reset the primary object's parameters and then restore them again. Having the ability to create and optionally save multiple named database objects with sqlYoga is really handy in those situations. Bob On Aug 7, 2012, at 6:53 PM, Alejandro Tejada wrote: > Andre Garzia-3 wrote >> >> The library is tested and targeted at SQLite databases but it works >> with any database supported by RevDB (with a sane SQL standard) >> > > How different is this library from SQLYoga? > > Al _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
