[sqlite] Segfault during FTS index creation from huge data

I don't know if it actually causes a problem, but isn't the "?command.Dispose()" not needed? Doesn't the "using" take care of disposing? Graham. Sent from Samsung Mobile Original message From: Artem Date: 28/04/2015 14:29 (GMT+00:00) To: General

[sqlite] Segfault during FTS index creation from huge data

I don't know if it will actually cause problems, but is the "?command.Dispose()" needed? Doesn't the "using" handle disposing? Graham Sent from Samsung Mobile Original message From: Artem Date: 28/04/2015 14:29 (GMT+00:00) To: General Discussion of

[sqlite] Segfault during FTS index creation from huge data

On Tue, Apr 28, 2015 at 5:06 PM, Simon Slavin wrote: > > On 28 Apr 2015, at 11:49pm, Scott Robison wrote: > > > I never saw a segfault in my case, though I never tried anything on any > > posix style system. It was strictly Windows. > > Windows doesn't call it segfault. It will report an

[sqlite] Segfault during FTS index creation from huge data

On Tue, Apr 28, 2015 at 4:27 PM, Artem wrote: > > That's not a segfault, though, is it. > > When I did the same in linux version of SQLite - I saw > the "Segmentation Fault" error. > I never saw a segfault in my case, though I never tried anything on any posix style system. It was strictly

[sqlite] Segfault during FTS index creation from huge data

No, I'm sure that is not a problem in my software, it exactly error of the SQLite library. My software is very simple - it creates simple connection to the database with connection string like "Data Source={0};New=false;Journal Mode=Off;Synchronous=Off;FailIfMissing=True" and executes a query like

[sqlite] Segfault during FTS index creation from huge data

> On 04/03/2015 10:16 PM, Artem wrote: >> Hi! >> >> The situation is like that. There?s a SQLite database with around 3 billion >> records. Each record consists of a certain CHAR field and several other >> additional fields with different types. The file size is approx. 340 gb. The >> maximum

[sqlite] building SQLite DLL with Visual C++

Bill & Steve Thanks guys I am trying to learn and make some progress with the information you both provided. On Mon, Apr 27, 2015 at 9:57 AM, Steven M. McNeese < steven.mcneese at freedomparkdfw.com> wrote: > Jay, > > I don't do VB.Net development but it should be very similar to C#.Net in >

[sqlite] Segfault during FTS index creation from huge data

On Tue, Apr 28, 2015 at 1:05 PM, Dan Kennedy wrote: > I just took a quick glance at the FTS code. As I said, it has been a couple >>> years, but this looks like the malloc that was failing for me at the >>> time: >>> http://www.sqlite.org/cgi/src/artifact/81f9ed55ad586148?ln=2473 >>> >> >> That

[sqlite] Segfault during FTS index creation from huge data

Getting "NoMem" sounds very much like a memory leak somewhere, with the most likely place being your own application, followed by the wrapper you are using, the FTS code and lastly the SQLite core. Lastly because the SQLite core is extensively tested with an explicit emphasis on not leaking

[sqlite] Segfault during FTS index creation from huge data

On Tue, Apr 28, 2015 at 1:03 PM, Dan Kennedy wrote: > On 04/29/2015 01:55 AM, Scott Robison wrote: > >> I just took a quick glance at the FTS code. As I said, it has been a >> couple >> years, but this looks like the malloc that was failing for me at the time: >>

[sqlite] Segfault during FTS index creation from huge data

On Tue, Apr 28, 2015 at 7:08 AM, Hick Gunter wrote: > Getting "NoMem" sounds very much like a memory leak somewhere, with the > most likely place being your own application, followed by the wrapper you > are using, the FTS code and lastly the SQLite core. Lastly because the > SQLite core is

[sqlite] Index causes slow queries: any thoughts?

>> In the middle of all that, after the line >> CREATE INDEX idx_Appointment_SaleItemUUID ON Appointment >> (Appointment_SaleItemUUID); >> is some slightly odd output - that's just as it appears in the command line >> output in Terminal on my Mac. > What does "PRAGMA integrity_check;" say about

[sqlite] SQLite and Scientific Computing: Arrays and Complex Numbers

On Tue, Apr 28, 2015 at 4:16 AM, James K. Lowden wrote: > A major hurdle is the > memory model: because array-programming libraries normally mandate the > data be in contiguous memory, there's a cost to converting to/from the > DBMS's B+ tree. The more array-like the physical storage of the

[sqlite] Segfault during FTS index creation from huge data

How about trying the sqlite3.exe command line utility. put your sql for that operation in a text file, launch the program, open the database, then read in the sql file with the .read command. If the error occurs, then possibly sqlite3. if not then it is probably something else.