Does anyone have a work around for ticket 923 (described below)? Is this perhaps not considered a bug?
When dumping an Sqlite 2.8.16 database, the data in the dump file is enclosed in single quotes except for fields containing only digits [0-9]. This is the case even if the fields are declared VARCHAR. I have many fields which have leading zeros. When I import these fields into Sqlite 3.x, the leading zeros are discarded. The only solution I currently have is to make several hundreds of very careful edits to the dump file to insert single quotes around the numbers with leading zeros prior to importing the dump file into Sqlite 3.x. This method is not fun and is prone to errors. Dr. Hipp, can you please comment on ticket 923? Thank you. Shawn M. Downey MPR Associates 632 Plank Road, Suite 110 Clifton Park, NY 12065 518-371-3983 x3 (work) 860-508-5015 (cell) -----Original Message----- From: Downey, Shawn Sent: Monday, July 11, 2005 4:07 PM To: sqlite-users@sqlite.org Subject: [sqlite] Ticket 923 status (missing quotes in 2.8.15 .dump...) Hello, I recently had some troubles converting a database from v2.8.0 to v3.08 per the following commands (under Windows XP): sqlite ddg53.db .dump >ddg53.dump sqlite3 ddg53.db3 ".read ddg53.dump" The dump of the 2.8.0 database did not enclose varchar fields containing numbers with leading zeros in single quotes. As a result of this, the import into 3.08 dropped the leading zeros on those fields. This is exactly the problem identified in ticket number 923. Does anyone have a status on this? Thank you. Shawn M. Downey MPR Associates 632 Plank Road, Suite 110 Clifton Park, NY 12065 518-371-3983 x3 (work) 860-508-5015 (cell)
