![]() My SQL QUERY: t = (playerid, mapid, timeTaken, (time() if not dateOverwrite else dateOverwrite), runID, runLeaveZoneVelocity, EnterZoneVelocity, averageVelocity, time()) I am now quite familiar with SQLite databases, their design, structure and how to write fairly complex queries.I am just getting an weird error: IntegrityError: UNIQUE constraint failed: ayer_id, jumptimes.map_id, nID My LambTracker program is based on an SQLite Database so I have all sorts of tools I use. LambTracker has 58 tables with another 12 in planning stages By way of comparison here is some info for you on relative complexity of the 3 main SQLite databases I've played with. I have poked at the Lightroom database and at the Quicken 2015 database. ![]() Right now my go to reference is The Definitive Guide to SQLite by Grant Allen and Mike Owens. (I'd only used hierarchical databases before I developed LambTracker) The tools I come back to all the time are the SQLite Manager plug-In for Firefox, SQLite Manger from SQLabs » sqlite database management tools and server (confusing that they have the same name, they are different) and very rarely SQLite Studio from įor learning basic relational database design stuff I loved the book Beginning Database Design by Clare Churcher. I am now quite familiar with SQLite databases, their design, structure and how to write fairly complex queries. Obviously changing things is a whole different level of commitment than looking around.Ĭlick to expand.My LambTracker program is based on an SQLite Database so I have all sorts of tools I use. The other day I tried finding where the XMP/IPTC Date Created was, and finally just gave up - it's not stored consistently, and I could never find a query to give the same value all the time as Lightroom (notably its absence, my guess due to some defaulting). For example, I run a quick report each year showing all galleries with a certain word in the name, in the calendar year, as it represents trips to those locations for tax purposes. If you are looking for something simple it is easy. ![]() This is especially true in publishing related plugins, as I do not think the API provides a mechanism to extend the database, so they just stuff data tables inside of columns. You'll find some columns, for example, with metadata stored as XML and value pairs (and sometimes both) all stuffed in a single column, not normalized out at all. The areas where it becomes very confusing are those areas you can tell were added later, and someone said "screw normalization just stuff it in there". Things you might think of as the "original" Lightroom are really quite well structured. You can also see how it handles root file moves, etc. GUID's used in addition to integer keys, why?) but you can pretty quickly track through (as an example) the image to the folder to the root, to form the path name to a file. You have no documentation, so you have to read between the lines, and sometimes wonder (e.g. ![]() ![]() Like most legacy databases, there is good and bad. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |