Re: [sqlite] Versioning in SQL database?
Many thanks again, I'll give it a try.. Best, randall
Re: [sqlite] Versioning in SQL database?
On Wed, Feb 08, 2006 at 08:33:48AM +0100, Arjen Markus wrote: > Paul Tomblin wrote: > > > > I am putting together something that will act like a Wiki for structured > > data (in this case, airport and navigation aid data like id, location, > > runways, etc). I currently store the data in an SQL databasee, but only > > the "current" version. I want to allow people to edit that data, but that > > means being able to compare versions, roll back erroneous edits, get what > > the database looked like before a particular editor came along, etc. Is > > there anything written on this topic? Has anybody ever tried it before? > > > > > > I recently saw something similar to what you describe (well, the airport > and navigation stuff) - http://www.flightaware.com - but maybe that is > just a similar area of application. Sounds pretty different. Flightaware tracks all flights currently in the air that are under the control of the air traffic system (basically, commercial flights and anyone who's filed an IFR flight plan). I actually know the folks behind the site. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Re: [sqlite] Versioning in SQL database?
"Randall" <[EMAIL PROTECTED]> wrote: > Thanks again! > I cannot see 3.3.2 at the download site..? > It is not on the download page, but you can probably guess the correct URL by making a minor change to the link for the 3.3.3 download. -- D. Richard Hipp <[EMAIL PROTECTED]>
Re: [sqlite] Versioning in SQL database?
Thanks again! I cannot see 3.3.2 at the download site..? You should be good to go if you use version 3.3.2. It doesn't have the fix that broke ".import" in version 3.3.3, but it does have the "if exists/if not exists" features introduced in version 3.3.0. HTH Dennis Cote
Re: [sqlite] Versioning in SQL database?
Randall wrote: Thanks, Catch 22; I can't upgrade because ".import" is not working again till 3.3.4! Best, Randall Randall, You should be good to go if you use version 3.3.2. It doesn't have the fix that broke ".import" in version 3.3.3, but it does have the "if exists/if not exists" features introduced in version 3.3.0. HTH Dennis Cote
Re: [sqlite] Versioning in SQL database?
Thanks, Catch 22; I can't upgrade because ".import" is not working again till 3.3.4! Best, Randall
Re: [sqlite] Versioning in SQL database?
Randall wrote: Hi, I acnnot get "IF EXISTS" to work for "DROP TABLE IF EXISTS tablename"; ver 3.2.8; I see "IF NOT EXISTS" started in ver 3.3.0, but "IF EXISTS" has been in the syntax page for at least months; am I doing something wrong? Randall Randal, It works fine for me in version 3.3.2. See the sqlite shell session below. SQLite version 3.3.2 Enter ".help" for instructions sqlite> drop table t; SQL error: no such table: t sqlite> drop table if exists t; sqlite> create table t(a,b); sqlite> select name from sqlite_master; t sqlite> drop table if exists t; sqlite> select name from sqlite_master; sqlite> This feature was first implemented in version 3.3.0, so you will need to upgrade from version 3.2.8. HTH Dennis Cote
Re: [sqlite] Versioning in SQL database?
Hi, I acnnot get "IF EXISTS" to work for "DROP TABLE IF EXISTS tablename"; ver 3.2.8; I see "IF NOT EXISTS" started in ver 3.3.0, but "IF EXISTS" has been in the syntax page for at least months; am I doing something wrong? Randall
Re: [sqlite] Versioning in SQL database?
- Original Message - From: "Jim C. Nasby" <[EMAIL PROTECTED]> To: <sqlite-users@sqlite.org> Sent: Wednesday, February 08, 2006 8:58 AM Subject: Re: [sqlite] Versioning in SQL database? On Tue, Feb 07, 2006 at 10:55:27AM -0500, Paul Tomblin wrote: I am putting together something that will act like a Wiki for structured data (in this case, airport and navigation aid data like id, location, runways, etc). I currently store the data in an SQL databasee, but only the "current" version. I want to allow people to edit that data, but that means being able to compare versions, roll back erroneous edits, get what the database looked like before a particular editor came along, etc. Is there anything written on this topic? Has anybody ever tried it before? I would add a version column to the appropriate tables and create views that pull the most recent version of everything. Or if performance becomes an issue, keep a table with only the current versions, and a seperate table with either all older versions or just all versions. An added benefit of a version field is it's a trivial way to detect potential conflicts; if you have the edit code pass back the version it was editing, you can verify that that version is what's still in the database. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Re: [sqlite] Versioning in SQL database?
Paul Tomblin wrote: > > I am putting together something that will act like a Wiki for structured > data (in this case, airport and navigation aid data like id, location, > runways, etc). I currently store the data in an SQL databasee, but only > the "current" version. I want to allow people to edit that data, but that > means being able to compare versions, roll back erroneous edits, get what > the database looked like before a particular editor came along, etc. Is > there anything written on this topic? Has anybody ever tried it before? > > I recently saw something similar to what you describe (well, the airport and navigation stuff) - http://www.flightaware.com - but maybe that is just a similar area of application. Regards, Arjen
Re: [sqlite] Versioning in SQL database?
On Tue, Feb 07, 2006 at 10:55:27AM -0500, Paul Tomblin wrote: > I am putting together something that will act like a Wiki for structured > data (in this case, airport and navigation aid data like id, location, > runways, etc). I currently store the data in an SQL databasee, but only > the "current" version. I want to allow people to edit that data, but that > means being able to compare versions, roll back erroneous edits, get what > the database looked like before a particular editor came along, etc. Is > there anything written on this topic? Has anybody ever tried it before? I would add a version column to the appropriate tables and create views that pull the most recent version of everything. Or if performance becomes an issue, keep a table with only the current versions, and a seperate table with either all older versions or just all versions. An added benefit of a version field is it's a trivial way to detect potential conflicts; if you have the edit code pass back the version it was editing, you can verify that that version is what's still in the database. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
[sqlite] Versioning in SQL database?
I am putting together something that will act like a Wiki for structured data (in this case, airport and navigation aid data like id, location, runways, etc). I currently store the data in an SQL databasee, but only the "current" version. I want to allow people to edit that data, but that means being able to compare versions, roll back erroneous edits, get what the database looked like before a particular editor came along, etc. Is there anything written on this topic? Has anybody ever tried it before? -- Paul Tomblin <[EMAIL PROTECTED]> http://xcski.com/blogs/pt/ Ahhh, the permie offer. The "Please sign up with us clueless fsckwits so you can spend all your time digging us out at a pittance" offer. -- Dan Holdsworth
