#9885 closed defect (worksforme)
forward slash at end-of-line in code block does not migrate
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
if I create a code block (drawing) like
------------- / / -------------
and do
sqlite3 "db/trac.db" ".dump" > dimpfile
to save the trac db (for migration)
and then do a
cat dumpfile | sqlite3 "${tracDb}"
then the figure becomes
------------- ; ; -------------
CentOS 5.5 (x86_64) trac 0.10.5-3.el5 sqlite 3.3.6-5
Attachments (0)
Change History (5)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
diff -u testdump.txt testdump2.txt
gives me
-PRAGMA foreign_keys=OFF; BEGIN TRANSACTION; CREATE TABLE test( t text ); INSERT INTO "test" VALUES(' ------------- - / - / +; +; -------------'); COMMIT;
comment:3 by , 14 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Well, it's indeed an issue with SQLite, not with Trac. I've been able to reproduce this by recompiling a sqlite-3.3.6 version. However, I couldn't find that version on sqlite.org, so I had to pick it up from a … CentOS .rpm, so I can't tell for sure it's genuine SQLite bug or one introduced by CentOS modifications.
The release notes of 3.3.9 talks about some fixes in .dump, so that might be related.
In any case, you should upgrade to a newer version of SQLite which doesn't have the problem (I tested 3.6.6 which worked, for example).
comment:4 by , 14 years ago
I create a RHEL bug report: https://bugzilla.redhat.com/show_bug.cgi?id=659349
comment:5 by , 14 years ago
I also created a CentOS bug report: http://bugs.centos.org/view.php?id=4654
And now I'm adding some text here to get through the spam filter
It looks more like a sqlite issue…
Can you try the following check? Given a file
testdump.txt
containing:Load this into a new db:
And dump it back:
Then, what does
diff -u testdump.txt testdump2.txt
give you?