On Sat, 3 May 2008 15:50:43 -0700, you wrote:
I've been using SQLite on my windows box and wanted to move some things to
the web. I found SQL Maestro's PHP Generator and it looked like it would be
very useful. I downloaded and all seem to work as advertised for generating
the php scripts. (In
I'm a beginning sqlite user (v3.5.8 for Linux). I use a c++ program to
open a connection to my database with no issues, but when trying to
exec any sql statements after that, i get SQLITE_BUSY (i.e. database
is locked). Here is the code I use:
int main() {
sqlite3 *db;
int ret; //
Zbigniew,
You can try SQLite Studio http://sqlitestudio.one.pl/
Thank you,
Malcolm
PS: For those following this thread, SQLite Studio is now (as of May 3
2008) a free product with GPL license.
___
sqlite-users mailing list
sqlite-users@sqlite.org
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
You define a callback in your CREATE statement. Why? Where is it?
[EMAIL PROTECTED] wrote:
I'm a beginning sqlite user (v3.5.8 for Linux). I use a c++ program to
open a connection to my database with no issues, but when trying to
exec any sql statements after that, i get SQLITE_BUSY
Hey folks,
We've started to see a crash in syncJournal that happens in the same
place in a previously mentioned e-mail to this list:
http://www.mail-archive.com/sqlite-users@sqlite.org/msg29637.html
We don't have any steps to reproduce, but we have a bug tracking the issue: