At 23:19 04/05/2008, you wrote:
If you use svn only to sync over many pc maybe you can put your project on a
usb device (or usb hd) so you don't need to sync with svn.
If you WANT to use svn and you are under linux you can create an alias for
commit that make a dump of your db then commit it and
On Sun, May 04, 2008 at 10:36:47PM +0200, M. Emal Alekozai scratched on the
wall:
Hi,
In the BIG db I have worked on there is a table that log every insert/update
on specific and important tables and a log of every sql statement execute
but I haven't ever see a db under version control
Hi,
In the BIG db I have worked on there is a table that log every insert/update
on specific and important tables and a log of every sql statement execute
but I haven't ever see a db under version control with svn (or csv or git or
any other).
I'm (mis)using subversion more as a
If you use svn only to sync over many pc maybe you can put your project on a
usb device (or usb hd) so you don't need to sync with svn.
If you WANT to use svn and you are under linux you can create an alias for
commit that make a dump of your db then commit it and one alias that update
and read
On May 4, 2008, at 4:36 PM, M. Emal Alekozai wrote:
Hi,
In the BIG db I have worked on there is a table that log every
insert/update
on specific and important tables and a log of every sql statement
execute
but I haven't ever see a db under version control with svn (or csv
or git or
In the BIG db I have worked on there is a table that log every insert/update
on specific and important tables and a log of every sql statement execute
but I haven't ever see a db under version control with svn (or csv or git or
any other).
--
[image: Just A Little Bit Of
Dear Sqlite users,
I want to put a sqlite database under version control (in my case subversion).
As far as I know the sqlite database is a binary file.
Always exporting and importing the database to a sql file is quite laborious .
What is the standard approach for this ?
Is there any filter