On 6 Mar 2012, at 1:34pm, Larry Knibb wrote:
> I wouldn't initially need to support schema changes, just data
> changes. And actually only data additions (INSERTs) as the first use
> case. So diffing the .dumps would probably suffice. But later, I'd
> want to handle UPDATE and DELETE.
If you ha
I wouldn't initially need to support schema changes, just data
changes. And actually only data additions (INSERTs) as the first use
case. So diffing the .dumps would probably suffice. But later, I'd
want to handle UPDATE and DELETE.
I'm sure I can write a small utility in Perl but just wanted to c
On 6 Mar 2012, at 1:19pm, Larry Knibb wrote:
> Is there already an established mechanism for diffing two SQLite
> databases and creating a SQL patch file?
>
> So not a GUI diff tool (like
> http://download.cnet.com/SQLite-Diff/3000-10254_4-205921.html) for
> looking at the diffs, but something
Is there already an established mechanism for diffing two SQLite
databases and creating a SQL patch file?
So not a GUI diff tool (like
http://download.cnet.com/SQLite-Diff/3000-10254_4-205921.html) for
looking at the diffs, but something to generate the SQL to upgrade an
old database to a new one.
4 matches
Mail list logo