Hi
I use LFSLapper, which since a number of releases ago, now saves driver lap times, etc., in SQLite databases, rather than in a txt file.
With some of these newer releases, I've usually copied the SQLite database data from one release over to another.
Only thing is, I use 2 different host operators to run a server each, and although they both support LFSLapper, they haven't always kept up with the releases (not their fault, as some of the releases have been minor, but frequent).
Problem I have, is that I now have a number of different SQLite databases, including copies from old releases, that I would like to merge together to give me a definative master database that I can use.
I would also like every so often to merge the databases from both servers, and use that as the new master.
i.e..
Then put SQL_Master on both servers, overwriting both originals.
Later, take databases from both servers and merge to make newer master () which, again, would be loaded onto both servers. SQL_Mas1_Serv1+SQL_Mas1_S2=SQL_M2. And continue the process.
Process-
Unfortunately, I don't know how to use SQLite, and though I've been reading up on it, I'm finding I'm not understanding it at all.
I can't seem to make the jump from MS Access, which I've been using for over 10 years (as well as Paradox [DOS and Windows versions] before that) to SQLite.
So.
Is there a free gui type SQL program that will take my 2 SQL databases, merge them, remove all the duplicates (likely to be many), then (the hardest part), where someone has done the same car/track combo again and if new lap time is faster (one or more of the individual time sectors may actually be slower), remove slower lap time entry. Don't want a !top table that shows multiple entries for same driver in same car on same track.
Or if no SQL program that will do that automatically (highly unlikely), a free SQL program with additional query, specially written by yourself(!), that will do same thing? Then output data into new database using same database files formats (.dbs + .elp) that LFSLapper will understand and add to.
Copy of some old database files attached, along with output table (!top).
I use LFSLapper, which since a number of releases ago, now saves driver lap times, etc., in SQLite databases, rather than in a txt file.
With some of these newer releases, I've usually copied the SQLite database data from one release over to another.
Only thing is, I use 2 different host operators to run a server each, and although they both support LFSLapper, they haven't always kept up with the releases (not their fault, as some of the releases have been minor, but frequent).
Problem I have, is that I now have a number of different SQLite databases, including copies from old releases, that I would like to merge together to give me a definative master database that I can use.
I would also like every so often to merge the databases from both servers, and use that as the new master.
i.e..
Then put SQL_Master on both servers, overwriting both originals.
Later, take databases from both servers and merge to make newer master () which, again, would be loaded onto both servers. SQL_Mas1_Serv1+SQL_Mas1_S2=SQL_M2. And continue the process.
Process-
Unfortunately, I don't know how to use SQLite, and though I've been reading up on it, I'm finding I'm not understanding it at all.
I can't seem to make the jump from MS Access, which I've been using for over 10 years (as well as Paradox [DOS and Windows versions] before that) to SQLite.
So.
Is there a free gui type SQL program that will take my 2 SQL databases, merge them, remove all the duplicates (likely to be many), then (the hardest part), where someone has done the same car/track combo again and if new lap time is faster (one or more of the individual time sectors may actually be slower), remove slower lap time entry. Don't want a !top table that shows multiple entries for same driver in same car on same track.
Or if no SQL program that will do that automatically (highly unlikely), a free SQL program with additional query, specially written by yourself(!), that will do same thing? Then output data into new database using same database files formats (.dbs + .elp) that LFSLapper will understand and add to.
Copy of some old database files attached, along with output table (!top).