|
2012-01-28
| ||
| 21:09 | • Fixed ticket [232637c465]: Dump code fails with 1002 columns plus 2 other changes (artifact: 366e3001fd user: drh) | |
| 21:08 | Update the .dump command of the command-line shell so that it (1) avoids putting the semicolon of a DDL statement on the same line as a comment, (2) avoids long expression, even when dumping a table with many columns, and (3) avoids unnecessary quoting of the table name. This fixes tickets [c04a8b8a4f] and [232637c465]. Shell change only; no changes to the SQLite core. (check-in: e6eea8d50d user: drh tags: trunk) | |
| 19:14 | • New ticket [232637c465] Dump code fails with 1002 columns. (artifact: 7a83bc5181 user: rogerb) | |
| Ticket Hash: | 232637c465fd13df525a3116c1ea77c03e660d42 | ||
| Title: | Dump code fails with 1002 columns | ||
| Status: | Fixed | Type: | Code_Defect |
| Severity: | Important | Priority: | Immediate |
| Subsystem: | Shell | Resolution: | Fixed |
| Last Modified: |
2012-01-28 21:09:25 13.48 years ago |
Created: |
2012-01-28 19:14:55 13.48 years ago |
| Version Found In: | 3.7.10 | ||
| Description: | ||||
|
Reported on the mailing and confirmed: http://thread.gmane.org/gmane.comp.db.sqlite.general/71527
When you have more than ~1,000 columns, the SQL text constructed in dump_callback() that generates the INSERT statement results in SQLITE_ERROR: Expression tree is too large (maximum depth 1000). This could be addressed by generating the column values another way such as retrieving them directly rather than via formatting SQL statements as queries. | ||||