Bug 659349 - reading dump file containing lines (regex) '[[:space:]]+/$' corrupts database
Summary: reading dump file containing lines (regex) '[[:space:]]+/$' corrupts database
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sqlite
Version: 5.5
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: rc
: ---
Assignee: Panu Matilainen
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-02 15:41 UTC by Ferry Huberts
Modified: 2013-03-26 09:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-26 09:49:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ferry Huberts 2010-12-02 15:41:05 UTC
Description of problem:


Version-Release number of selected component (if applicable):
sqlite 3.3.6-5


How reproducible:
always

Steps to Reproduce:
1. create a file 'testdump.txt' with:

PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
CREATE TABLE test( t text );
INSERT INTO "test" VALUES('               -------------
              /
             /
-------------');
COMMIT;


2. Load it into a new db with:
     cat testdump.txt | sqlite3 ttt
3. And dump it with:
     sqlite3 ttt .dump > testdump2.txt
4. Now compare the 2 files:
     diff -u testdump.txt testdump2.txt
5. And see:

-PRAGMA foreign_keys=OFF;
 BEGIN TRANSACTION;
 CREATE TABLE test( t text );
 INSERT INTO "test" VALUES('               -------------
-              /
-             /
+;
+;
 -------------');
 COMMIT;




  
Actual results:
The diff on the PRAGMA line is not really relevant, but the other 2 lines are!


Expected results:
no diff (except maybe for the pragma line)

Additional info:

this seems to be fixed in sqlite 3.6.6

see http://trac.edgewall.org/ticket/9885

Comment 1 Ferry Huberts 2010-12-02 15:43:27 UTC
This corrupts my data when I migrate sqlite databases, which is why I set it to urgent

Comment 2 Ferry Huberts 2010-12-02 15:57:01 UTC
see also http://bugs.centos.org/bug_view_advanced_page.php?bug_id=4654

Comment 3 Ferry Huberts 2011-03-03 12:25:53 UTC
Why is there not activity on this bug?

It is corrupting my data

Comment 4 Ferry Huberts 2011-04-11 07:38:55 UTC
ping

Comment 5 Jan Zeleny 2013-03-26 09:49:33 UTC
Even though we acknowledge the seriousness of this issue, RHEL5 is at very late stage of its development cycle and this issue should be fixed in later versions of RHEL.

Taking that into consideration, I'm closing the bug as WONTFIX. The fix for this bug would take a serious amount of time and it would have a potential to break things, which is not acceptable at this late stage of development cycle.

If you experience the same problem in later versions of RHEL, feel free to clone this bug for them.


Note You need to log in before you can comment on or make changes to this bug.