[sqlite] Corrupted database

On 2015-03-16 09:49 PM, Dave Dyer wrote: >> Do you still have a copy of the originally damaged Database? I believe a >> closer look to it will reveal more corruption than the assumed. > I have the original database. What other tests could I do to look for > evidence? > > It appears (so far)

[sqlite] Searching for interfacing info with Liberty Basic

I've been using Liberty Basic 4.04 as a hobby language for about twelve years now. In that time I never programmed anything that needed a real database. Now I have that need and I would like to use sqlite because of its many advantages. I know enough about (relational) databases and how they work

[sqlite] Corrupted database

On 2015-03-16 08:35 PM, Dave Dyer wrote: > I have some addition evidence that there is an underlying problem, > exacerbated by some failure in SMB file sharing. > > In this instance, there is a set of duplicated records that did not > directly cause an indexing error, but which could have been

[sqlite] Searching for interfacing info with Liberty Basic

And this: http://www.libertybasicuniversity.com/lbnews/nl106/SQLite.htm -- Bill Drago Senior Engineer L3 Narda-MITEQ 435 Moreland Road Hauppauge, NY 11788 631-272-5947 / William.Drago at L-3COM.com > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org

[sqlite] Searching for interfacing info with Liberty Basic

This is old, but may still be useful to you: http://libertybasicuniversity.com/lbnews/nl105/sql.htm -- Bill Drago Senior Engineer L3 Narda-MITEQ 435 Moreland Road Hauppauge, NY 11788 631-272-5947 / William.Drago at L-3COM.com > -Original Message- > From: sqlite-users-bounces at

[sqlite] Documentation typo

On this page: http://www.sqlite.org/queryplanner.html Under the heading 1.4 Multiple Result Rows the word "of" is missing between the words "instead" and "peaches" in the third sentence. -- Bill Drago Senior Engineer L3 Narda-MITEQ 435 Moreland Road Hauppauge,

[sqlite] When to disambiguate column names in queries?

Ryan & Dave, Thank you for the replies. It's nice to know my thinking is on the right track. Regards, -- Bill Drago Senior Engineer L3 Narda-MITEQ 435 Moreland Road Hauppauge, NY 11788 631-272-5947 / William.Drago at L-3COM.com > -Original Message- > From: sqlite-users-bounces at

[sqlite] When to disambiguate column names in queries?

On 2015-03-16 06:16 PM, Drago, William @ CSG - NARDA-MITEQ wrote: > All, > > Some of my Select statements are pretty long and I'm starting to think it'd > be a good idea to always include table names of columns instead of just when > they are not unique. This would make the Select statements

[sqlite] Corrupted database

On 16 Mar 2015, at 6:35pm, Dave Dyer wrote: > This "fully repaired" database turned out to contain a duplicated set of > records which did not cause an indexing problem, but which should not have > occurred, and was consistent with a duplicated transaction. If this had > been caused by a

[sqlite] FAQ typo

On 3/16/15, O.Zolotov wrote: > Dear All, > the FAQ's item 21 ( http://www.sqlite.org/faq.html ) has a typo. The > sentences > > " Your can use PRAGMA integrity_check > Your can use PRAGMA quick_check ..." > > are more likely to be > " You can use PRAGMA integrity_check > You can use

[sqlite] Corrupted database

>I will have to say very sadly that if you absolutely have to have a >system where the DB file is not on the exact same machine (physical) >than the client software (the bit using SQLite code), then SQLite is not >a good choice - consider MySQL or Postgres perhaps. There was a crowd >some time

[sqlite] When to disambiguate column names in queries?

Personally, I'd format it like this to be the most readable: SELECT PH.POrderas POrder, PH.EntryDate as EntryDate, PH.ClientCodeas ClientCode, CL.ClientNameas ClientName, PM.Lines as Lines, PD.LineNo

[sqlite] FAQ typo

Not personally familiar with Russian translation issue, but thanks for the English language spell check should use "You" instead of "Your" in cited sentences. Jim Callahan Orlando, FL On Mon, Mar 16, 2015 at 5:19 PM, O.Zolotov wrote: > Dear All, > the FAQ's item 21 (

[sqlite] Is 'synchronous' pragma now being set on per database basis?

> On 3/16/15, Paul wrote: > > > Is doc page is > > outdated and 'synchronous' pragma is now set for each databse separately? > > It has always been that way. The documentation has recently been > updated to clarify that point. See >

[sqlite] When to disambiguate column names in queries?

If you design your database schemas such that, where possible, corresponding columns have the same names in all tables, and you do natural joins, the problem will basically go away. -- Darren Duncan On 2015-03-16 9:16 AM, Drago, William @ CSG - NARDA-MITEQ wrote: > All, > > Some of my Select

[sqlite] When to disambiguate column names in queries?

Hi Bill, I'm not sure about the 'sqlite world', most of my sql work is done using a different dbms, but my 'standard' is to always use alias names anytime I have two or more tables in a SELECT. Yes, it can make the sql longer and sometimes it is not strictly necessary (as you say, only needed

[sqlite] Documentation typo

On 3/16/15, Drago, William @ CSG - NARDA-MITEQ wrote: > On this page: > > http://www.sqlite.org/queryplanner.html > > Under the heading 1.4 Multiple Result Rows the word "of" is missing > between the words "instead" and "peaches" in the third sentence. Thanks for the report. Fixed at

[sqlite] Is 'synchronous' pragma now being set on per database basis?

Hello, fellow developers. Recently we performed a lot of test with ZFS and Sqlite and long story short: we came up with a conclusion that it is safe to disable fsync() to keep database consistent (though not durable), even in case of power failure. So we decided to stck with? 'PRAGMA

[sqlite] When to disambiguate column names in queries?

All, Some of my Select statements are pretty long and I'm starting to think it'd be a good idea to always include table names of columns instead of just when they are not unique. This would make the Select statements longer, but perhaps easier to understand if the reader knows where each

[sqlite] Escaping strings in custom FTS tokenizer

Hello all, Another question: in my application I have a FTS4 virtual table that I am writing a custom tokenizer for. I can't find any documentation on what symbols are "safe" to include in the index, and which ones are not because they have special meaning in an FTS query. For example: if my

[sqlite] Corrupted database

On 3/16/15, Simon Slavin wrote: > > Because of the format in which SQLite keeps its indexes, you > cannot always repair a corrupted index by deleting the rows which you think > are corrupt. Sometimes you need to delete other rows too (for example those > immediately before and after a corrupt

[sqlite] minor documentation flaw

In https://sqlite.org/lang_expr.html, the anchor appears twice. Obviously the scond occurence should be Wolfgang

[sqlite] sqlite3_release_memory when SQLITE_THREADSAFE=0

Hi Simon, Well in my case the linked threadsafe.html documentation won't be helpful, because it looks like at runtime I can only downgrade as far as multi-thread mode, not single-thread mode, and it's in single-thread mode where I'm really seeing a significant performance advantage. I think the

[sqlite] Corrupted database

> >Do you still have a copy of the originally damaged Database? I believe a >closer look to it will reveal more corruption than the assumed. I have the original database. What other tests could I do to look for evidence? It appears (so far) that the database I reconstructed from the dump

[sqlite] Corrupted database

> >Do you still have a copy of the originally damaged Database? I believe a >closer look to it will reveal more corruption than the assumed. I have the original database. What other tests could I do to look for evidence? It appears (so far) that the database I reconstructed from the dump

[sqlite] Is 'synchronous' pragma now being set on per database basis?

On 3/16/15, Paul wrote: > when the usage is > > (1) open database > (2) execute 'PRAGMA synchronous = OFF;' > (3) attach database X > (4) execute 'PRAGMA X.synchronous = OFF;' > (5) begin transaction > (6) do some inserts/deletes/updates > (7) commit transaction > (8) close database > > I

[sqlite] Corrupted database

> >Do you still have a copy of the originally damaged Database? I believe a >closer look to it will reveal more corruption than the assumed. I have the original database. What other tests could I do to look for evidence? It appears (so far) that the database I reconstructed from the dump

[sqlite] Corrupted database

> >Do you still have a copy of the originally damaged Database? I believe a >closer look to it will reveal more corruption than the assumed. I have the original database. What other tests could I do to look for evidence? It appears (so far) that the database I reconstructed from the dump

[sqlite] Corrupted database

> >The only safe thing to do is to drop the index and remake it. Or do to >something which does that (e.g. VACUUM). As I said, the first step in my repair was to drop the offending index.

[sqlite] Corrupted database

> >The only safe thing to do is to drop the index and remake it. Or do to >something which does that (e.g. VACUUM). As I said, the first step in my repair was to drop the offending index.

[sqlite] Corrupted database

I have some addition evidence that there is an underlying problem, exacerbated by some failure in SMB file sharing. In this instance, there is a set of duplicated records that did not directly cause an indexing error, but which could have been created if a transaction failed (presumably due to a

[sqlite] Is 'synchronous' pragma now being set on per database basis?

On 3/16/15, Paul wrote: > >> On 3/16/15, Paul wrote: >> >> > Is doc page is >> > outdated and 'synchronous' pragma is now set for each databse >> > separately? >> >> It has always been that way. The documentation has recently been >> updated to clarify that point. See >>

[sqlite] Is 'synchronous' pragma now being set on per database basis?

On 3/16/15, Paul wrote: > Is doc page is > outdated and 'synchronous' pragma is now set for each databse separately? It has always been that way. The documentation has recently been updated to clarify that point. See

[sqlite] Memory leak?

Hello, sorry for the late answer. My weekend was full of events. > On 13 Mar 2015, at 23:32, Gregory Moore wrote: > > Are you interacting directly with sqlite? Or are you using a 3rd party API > such as FMDB? I take it you are not using Core Data (which optionally can > use a sqlite

[sqlite] BUG in 3.8.8.3 and pre-release: Wrong ERROR_DISK_FULL writing a blob on Windows

R.Smith wrote: > > > On 2015-03-16 12:49 AM, javaj1811 at elxala.com wrote: >> Hi Joe, >> >> good point, I've tested the fail scenario having the database located >> in a NTFS disk with the result of NO FAIL!!! >> so the insertion was done without sqlite error. >> now the problem seems to be

[sqlite] BUG in 3.8.8.3 and pre-release: Wrong ERROR_DISK_FULL writing a blob on Windows

On 2015-03-16 12:49 AM, javaj1811 at elxala.com wrote: > Hi Joe, > > good point, I've tested the fail scenario having the database located > in a NTFS disk with the result of NO FAIL!!! > so the insertion was done without sqlite error. > now the problem seems to be reduced to Windows and FAT32

[sqlite] BUG in 3.8.8.3 and pre-release: Wrong ERROR_DISK_FULL writing a blob on Windows

javaj1811 at elxala.com wrote: > Joe Mistachkin wrote: >> What file system is being used on the drive in question (e.g. FAT, >> FAT32, >> NTFS, etc)? >> >> -- >> Joe Mistachkin >> >> ___ >> sqlite-users mailing list >> sqlite-users at

[sqlite] BUG in 3.8.8.3 and pre-release: Wrong ERROR_DISK_FULL writing a blob on Windows

Joe Mistachkin wrote: > What file system is being used on the drive in question (e.g. FAT, FAT32, > NTFS, etc)? > > -- > Joe Mistachkin > > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org >