sqlite

mirrors/sqlite

Fork 0

Commit Graph

Author	SHA1	Message	Date
mistachkin	fda06befd5	Add retry logic for AV defense to winOpen. Also, refactor test suite to allow the key Tcl file operations (e.g. copy and delete) to be retried. FossilOrigin-Name: 9007586fdabed8dbcc78581ea9821cfd1f9a4c8c	2011-08-02 00:57:34 +00:00
shess	3438ea3b9e	http://www.sqlite.org/cvstrac/tktview?tn=2219 When creating fts tables in an attached database, the backing tables are created in database 'main'. This change propagates the appropriate database name to the routines which build sql statements. Note that I propagate the database name and table name separately. I briefly considered just making the table name be "db.table", but it didn't fit so well in the model used to store the table name and other information, and having the db name passed separately seemed a bit more transparent. (CVS 3631) FossilOrigin-Name: 283385d20724f0144f38de89bd179715ee5e738b	2007-02-07 01:01:17 +00:00

Author

SHA1

Message

Date

mistachkin

fda06befd5

Add retry logic for AV defense to winOpen. Also, refactor test suite to allow the key Tcl file operations (e.g. copy and delete) to be retried.

FossilOrigin-Name: 9007586fdabed8dbcc78581ea9821cfd1f9a4c8c

2011-08-02 00:57:34 +00:00

shess

3438ea3b9e

http://www.sqlite.org/cvstrac/tktview?tn=2219

When creating fts tables in an attached database, the backing tables
are created in database 'main'.  This change propagates the
appropriate database name to the routines which build sql statements.

Note that I propagate the database name and table name separately.  I
briefly considered just making the table name be "db.table", but it
didn't fit so well in the model used to store the table name and other
information, and having the db name passed separately seemed a bit
more transparent. (CVS 3631)

FossilOrigin-Name: 283385d20724f0144f38de89bd179715ee5e738b

2007-02-07 01:01:17 +00:00

2 Commits