I try both.
Depending on the data deleting or rewriting, I get 2 empty column, or just
empty(no column).
???:Richard Hippdrh at sqlite.org
???:SQLite mailing listsqlite-users at mailinglists.sqlite.org
:2015?12?2?(??)?21:31
??:Re: [sqlite] Why Corrupted DB File Cause No Error?
On
On 12/2/15, Bart Smissaert wrote:
>> and the SQLite query planner sometimes notes that length when considering
> data shape
>
> In what situations does that happen?
>
CREATE TABLE ex1(a INTEGER, b VARCHAR(5), c VARCHAR(5000));
CREATE INDEX ex1b ON ex1(b);
CREATE INDEX ex1c ON ex1(c);
SELECT *
I guess so too.
But, It can be happen in real scene.
A part of data may be lost by a low chance accident in the application
lifecycle. It would be very hard to find out this problem and fix it because of
causing no error.
???:Simon Slavinslavins at bigfraud.org
???:SQLite mailing
Thanks for your answer.
But you can see my example, I should get 2 column from testtable, but I get
none. It means that db is already reading the corrupted part but get nothing.
???:Stephan Bealsgbeal at googlemail.com
???:SQLite mailing listsqlite-users at mailinglists.sqlite.org
I make a database, create a table and insert some data.
And then delete a section of data manually using binary editor, result that I
can?t get any of column but SQLite does not give me a error message.
console log before db file corrupted:
sqlite .open test.db
sqlite select * from testtable;
On Wed, Dec 2, 2015 at 4:29 PM, R Smith wrote:
>
> Personally I use VARCHAR(Len) in table column definitions - simply because
> my schema is then directly interchangeable with MySQL/PostGres and the
> SQLite query planner sometimes notes that length when considering data
> shape - but for data
On 2 Dec 2015, at 4:34pm, Erwin Kalvelagen
wrote:
> I could not find a reference to this using Google. So my question is: Is
> this a known problem? I would like to understand a little bit better what
> this is about.
The bug, if there is a bug, must be in Excel/VBA. SQLite will accept
On Wed, Dec 2, 2015 at 2:34 PM, Erwin Kalvelagen
wrote:
> A user suggested that I should not use type TEXT but rather type VARCHAR for
> character columns, due to some issue with Excel/VBA.
If he or she turns out to be correct, do it. As Slavin and Hipp
mentioned, SQLite won't care about the
>> sqlite3 -header flexsql.db "select distinct text from v_term_item where
>> name='text' and lower(text) REGEXP('.*some_text.*');"
>> which doesn't works
>REGEXP is not compiled into SQLite by default.
>Simon.
Yes but in gentoo it is compiled. Only a problem with new lines
I tried
sqlite3 -header flexsql.db "select distinct text from v_term_item where
name='text' and lower(text) REGEXP('.*some_text.*');"
which doesn't works
sqlite3 -header flexsql.db "select distinct text from v_term_item where
name='text' and lower(text) like '%some_text%';"
works
so I tried a
On Wed, Dec 2, 2015 at 12:56 PM, sanhua.zh wrote:
> I guess so too.
> But, It can be happen in real scene.
>
A part of data may be lost by a low chance accident in the application
> lifecycle. It would be very hard to find out this problem and fix it
> because of causing no error.
>
It's a
On 2 Dec 2015, at 12:54pm, michael wrote:
> sqlite3 -header flexsql.db "select distinct text from v_term_item where
> name='text' and lower(text) REGEXP('.*some_text.*');"
> which doesn't works
REGEXP is not compiled into SQLite by default.
Simon.
On 12/2/2015 7:54 AM, michael wrote:
> sqlite3 -header flexsql.db "select distinct replace(lower(text),0x0A,'')
> from v_term_item where lower(text) REGEXP('.*some_text.*') limit 1;"
You are removing newlines in the wrong spot. Do it on the left-hand side
of REGEXP, not in SELECT clause.
The
On Wed, Dec 2, 2015 at 11:59 AM, sanhua.zh wrote:
> Why it does not show error, some thing like?Error: database disk image is
> malformed?? Is it a bug in SQLite?
>
because you didn't corrupt a part it actually read. Imagine if you have a
20GB db and you expect it to report such errors when you
You give no indication of the schema you are using or the statement that went
wrong.
If you can reproduce the error using the sqlite3 shell, then it is probably
within sqlite3. If not, then it is most probably your own program which is
causing the fault, maybe by passing incorrect (stale or
On 12/2/15, Erwin Kalvelagen wrote:
> Good morning.
>
> I wrote a little tool to dump certain data sets into a SQLite database. A
> user suggested that I should not use type TEXT but rather type VARCHAR for
> character columns, due to some issue with Excel/VBA. See the comments in:
>
On 2 Dec 2015, at 11:38am, Stephan Beal wrote:
> On Wed, Dec 2, 2015 at 11:59 AM, sanhua.zh wrote:
>
>> Why it does not show error, some thing like?Error: database disk image is
>> malformed?? Is it a bug in SQLite?
>
> because you didn't corrupt a part it actually read.
Looking at the
Good morning.
I wrote a little tool to dump certain data sets into a SQLite database. A
user suggested that I should not use type TEXT but rather type VARCHAR for
character columns, due to some issue with Excel/VBA. See the comments in:
On 12/2/15, sanhua.zh wrote:
> I make a database, create a table and insert some data.
> And then delete a section of data manually using binary editor,
Did you really "delete" the data, or did you simply change the data to
have all NULL content?
--
D. Richard Hipp
drh at sqlite.org
19 matches
Mail list logo
