Re: [sqlite] SQLite 3.24.0 Solaris 9 build failure

On 20/01/2019 15:03, Dennis Clarke wrote: On 1/19/19 10:55 AM, Igor Korot wrote: Dennis, On Sat, Jan 19, 2019 at 9:31 PM Dennis Clarke wrote: And SPARC version is still available for download... Let us know when you get that running. Install of x86 went very smooth. The x86_64

Re: [sqlite] Lazy JSON data to sqlite database

If you have an SQL schema that works for you and also sample data, I might be able to assist writing the conversion program. Dunno if you're interested since it sounds like you won't need to do this again for another year. On Sat, Jan 19, 2019, 23:17 David Bicking >> Is there a tool out there

Re: [sqlite] Lazy JSON data to sqlite database

>> Is there a tool out there that will more or less automate the task for >> me? Hopefully free, as no one is paying me to do this. (The other >> volunteers have maybe a dozen records in total and are doing their >> reports by hand. ) >The automation is at a lower level than you seem to

Re: [sqlite] SQLite 3.24.0 Solaris 9 build failure

On 1/19/19 10:55 AM, Igor Korot wrote: Dennis, On Sat, Jan 19, 2019 at 9:31 PM Dennis Clarke wrote: And SPARC version is still available for download... Let us know when you get that running. Install of x86 went very smooth. The x86_64 process is trivial. And I was able to compile

Re: [sqlite] SQLite 3.24.0 Solaris 9 build failure

Dennis, On Sat, Jan 19, 2019 at 9:31 PM Dennis Clarke wrote: > > > > And SPARC version is still available for download... > > Let us know when you get that running. Install of x86 went very smooth. And I was able to compile fairly recent SQLite with Oracle Studio 12.6 with just couple of

Re: [sqlite] SQLite 3.24.0 Solaris 9 build failure

And SPARC version is still available for download... Let us know when you get that running. Dennis ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Variable Declaration

I'm jumping into the middle of the conversation, possibly without seeing the beginning, but from what I've seen so far, it seems to me that the key is recognizing there are many tools in a programmer's toolbox. Each tool covers a certain area of functionality really well, then there are areas

Re: [sqlite] Variable Declaration

But then in BASH, for example, the temp table would only last for the life of the initial connection, so you'd have to throw everything in one execution. This goes along the lines of just setting a variable. A BIG time question comes to scope of the life of the variable. Does it live for the

Re: [sqlite] SQLite 3.24.0 Solaris 9 build failure

Dennis Clarke wrote: > On 1/19/19 4:47 PM, Andy Goth wrote: >> Dennis Clarke wrote: >>> On 2018-07-28 08:33, Andy Goth wrote: SQLite 3.24.0 fails to build on Solaris 9 (a.k.a. Solaris 2.9) >> >>> It may be [worth] while to spin up a Solaris 9 zone on a Solaris 10 >>> or Solaris 11 server for

Re: [sqlite] SQLite 3.24.0 Solaris 9 build failure

Hi, On Sat, Jan 19, 2019 at 4:29 PM Dennis Clarke wrote: > > On 1/19/19 4:47 PM, Andy Goth wrote: > > Dennis Clarke wrote: > >> On 2018-07-28 08:33, Andy Goth wrote: > >>> SQLite 3.24.0 fails to build on Solaris 9 (a.k.a. Solaris 2.9) > > > >> It may be [worth] while to spin up a Solaris 9 zone

Re: [sqlite] Lazy JSON data to sqlite database

David Bicking wrote: > I have a data file with JSON data, and I want to get the data into an > sqlite database so I can run queries against it. It is not a large file, > only about 600 records in the main table. I've never worked with JSON > before, and really don't want to write my own parser to

Re: [sqlite] SQLite 3.24.0 Solaris 9 build failure

On 1/19/19 4:47 PM, Andy Goth wrote: Dennis Clarke wrote: On 2018-07-28 08:33, Andy Goth wrote: SQLite 3.24.0 fails to build on Solaris 9 (a.k.a. Solaris 2.9) It may be [worth] while to spin up a Solaris 9 zone on a Solaris 10 or Solaris 11 server for this purpose. I don't have access to

Re: [sqlite] SQLite 3.24.0 Solaris 9 build failure

Dennis Clarke wrote: > On 2018-07-28 08:33, Andy Goth wrote: >> SQLite 3.24.0 fails to build on Solaris 9 (a.k.a. Solaris 2.9) > It may be [worth] while to spin up a Solaris 9 zone on a Solaris 10 or > Solaris 11 server for this purpose. I don't have access to any Solaris servers of any kind.

Re: [sqlite] Request for documentation improvement: transactions

Richard Hipp wrote: > On 1/19/19, andrew.g...@l3t.com wrote: > > I was actually thinking about this earlier today, how I'd signed the > > contributor agreement for SQLite at the same time as I did for Fossil, > > yet only ever asked for commit access for Fossil. Would you consider > > letting me

Re: [sqlite] Request for documentation improvement: transactions

On 1/19/19, andrew.g...@l3t.com wrote: > > I was actually thinking about this earlier today, how I'd signed the > contributor agreement for SQLite at the same time as I did for Fossil, yet > only ever asked for commit access for Fossil. Would you consider letting me > help with SQLite

Re: [sqlite] Request for documentation improvement: transactions

Richard Hipp wrote: > Here's the deal: I'm very fussy about who can contribute *code* to > SQLite, in order to protect the public-domain status of the SQLite > source code and due to the intense nature of testing required to land a > change. Sensible. I was wondering about your policy here,

Re: [sqlite] Variable Declaration

On Sat, Jan 19, 2019, 6:53 AM Simon Slavin > On 19 Jan 2019, at 4:49am, Stephen Chrzanowski wrote: > > > I know about the bindings. I don't know about all languages supporting it. > > Bindings are part of the SQLite API. Any language which can make SQLite calls should be supporting binding. >

Re: [sqlite] Variable Declaration

The reason for this is historical and is because Microsoft SQL Server is a derivative work of Sybase SQL Server and their TRANSACT-SQL language. Sybase was the first (I believe) SQL-based RDBMS that supported a complete and ONLY dynamic execution model for SQL statements. All other DBMS

Re: [sqlite] Request for documentation improvement: transactions

On 1/19/19, Simon Slavin wrote: > I suspect it [the docs] started out small and grew, without ever being > rewritten. That is a reasonable conjecture. I agree that the documentation could use some work. I will eventually get around to doing this, but I feel like making enhancements and fixing

[sqlite] Request for documentation improvement: transactions

concerns me. I suspect it started out small and grew, without ever being rewritten. (1) It explains four complicated issues and has no sections. I see two possibilities: either improve that page, or split it into (A) a short page which

Re: [sqlite] Variable Declaration

before -> because to help those for whom English is not their first language. Cheers. On 1/19/2019 5:53, Simon Slavin wrote: On 19 Jan 2019, at 4:49am, Stephen Chrzanowski wrote: I know about the bindings. I don't know about all languages supporting it. Bindings are part of the SQLite

Re: [sqlite] Database locking problems

On 19 Jan 2019, at 4:43pm, wrote: > I'm thinking one possible sequence might be: It's the right suggestion, but you're still in diagnostic stage, so this is a faster test: 1) Make sure your code still sets timeouts on every connection. 5000 ms should be fine. 2) Replace every BEGIN with

Re: [sqlite] Database locking problems

> Not sure if this is the problem you are running into, but it might be > because SQLite is detecting a potential deadlock. I think that's exactly what's going on. SQLite is not bothering with the busy handler since it already knows no amount of waiting will solve the problem. > When you just

Re: [sqlite] Database locking problems

Scott Vallery wrote: > have you considered 'threading'? This sounds like something that you need to > create a thread to do. Creating a thread should then allow you to set > parameters to wait until one process completes and switch back and forth. Yes, threads would make cooperation easier.

Re: [sqlite] Database locking problems

On 2019/01/19 5:20 PM, Richard Hipp wrote: On 1/19/19, R Smith wrote: "merged at some stage" and "merged into the next release" are different things. The latter will likely not happen, but I cannot say about the former, just yet. Thank you - I believe my original mail did say "... a next

Re: [sqlite] Database locking problems

On 1/19/19, R Smith wrote: > I make scripts/software for SQLite used by many, I > can dictate the lowest version number for a script, but usually they use > whatever engine is downloadable from the site (sqlite3.exe, sqlite3.dll > etc.), so if the very useful BEGIN CONCURRENT won't be merged at

Re: [sqlite] Database locking problems

On 2019/01/19 4:55 PM, Richard Hipp wrote: On 1/19/19, R Smith wrote: Hi RIchard, any chance this BEGIN CONCURRENT branch will make it into a next SQLite standard release? You can always pull it from the branch. The branch will not go away. Thank you kindly, this much is known. Allow me

[sqlite] Lazy JSON data to sqlite database

Okay, I know this is just me being lazy, but I have a data file with JSON data, and I want to get the data into an sqlite database so I can run queries against it. It is not a large file, only about 600 records in the main table. I've never worked with JSON before, and really don't want to

Re: [sqlite] Solaris Studio 12.6 compilation failure

On 1/18/19, Igor Korot wrote: > "sqlite3.c", line 29907: warning: conversion to double is out of range > "sqlite3.c", line 52491: warning: statement not reached > > Is it something to be worry? Probably not. But, without knowing precisely what version of SQLite you are compiling, the line

Re: [sqlite] Database locking problems

On 1/19/19, R Smith wrote: > Hi RIchard, any chance this BEGIN CONCURRENT branch will make it into a > next SQLite standard release? You can always pull it from the branch. The branch will not go away. -- D. Richard Hipp d...@sqlite.org ___

Re: [sqlite] Database locking problems

Hi RIchard, any chance this BEGIN CONCURRENT branch will make it into a next SQLite standard release? On 2019/01/19 3:07 PM, Richard Hipp wrote: If you are daring, you can also try building from the begin-concurrent branch (https://www.sqlite.org/src/timeline?r=begin-concurrent) and using

Re: [sqlite] Variable Declaration

On 19 Jan 2019, at 4:49am, Stephen Chrzanowski wrote: > I know about the bindings. I don't know about all languages supporting it. Bindings are part of the SQLite API. Any language which can make SQLite calls should be supporting binding. Using binding means you can have the variables you

Re: [sqlite] Variable Declaration

On 19-1-2019 14:49, Luuk wrote: This question is not about: 'parameter binding'! It's about 'variable decalaration'... oops 'variable declaration' ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] Variable Declaration

On 19-1-2019 14:23, Jesse Rittner wrote: What language do you want to use? Parameter binding is a feature of the SQLite C API. So pretty much any language with a C FFI will suffice. There's a list on Wikipedia, not sure how authoritative it is.

Re: [sqlite] Variable Declaration

What language do you want to use? Parameter binding is a feature of the SQLite C API. So pretty much any language with a C FFI will suffice. There's a list on Wikipedia, not sure how authoritative it is. https://en.wikipedia.org/wiki/SQLite#Programming_language_support (Note: When it says they

Re: [sqlite] Database locking problems

Not sure if this is the problem you are running into, but it might be because SQLite is detecting a potential deadlock. When you just use BEGIN, SQLite will acquire locks lazily - the first read operation will acquire a shared lock, and the first write operation will acquire a reserved lock. Any

Re: [sqlite] Database locking problems

Thanks for the detailed trouble analysis! Short answer: Probably you want to do "BEGIN IMMEDIATE" rather than just "BEGIN" to start your transaction. The busy timeout is not working because you start out your transaction using a read operation - the first SELECT statement - which gets a read

Re: [sqlite] Database locking problems

I'm a newbie on the block and this is my first  post, but have you considered 'threading'? This sounds like something that you need to create a thread to do. Creating a thread should then allow you to set parameters to wait until one process completes and switch back and forth. I've done this

Re: [sqlite] JOINning two tables provides no data

On January 18, 2019 12:54:32 PM EST, Jose Isaias Cabrera wrote: > >sqlite> select a.a, a.b, a.c, b.d, b.e as q from a join b on a.a=b.a >where a.a = 1; >sqlite> > >This provides no result. I expected to get, > >1|2|3|| You appear to seek the result of a LEFT JOIN. -- J. King

[sqlite] Database locking problems

I am having significant difficulty getting two process to not slam into each other when accessing the same database. The behavior I want is for one process to wait while the database is busy being written to by the other, but instead I immediately get SQLITE_BUSY. This is happening to me when

[sqlite] JOINning two tables provides no data

Greetings! Imagine this scenario, create table a (a, b, c); create table b (a, d, e); insert into a values (1, 2, 3); insert into a values (2, 3, 4); insert into a values (3, 4, 5); select a.a, a.b, a.c, b.d, b.e as q from a join b on a.a=b.a where a.a = 1; sqlite> select a.a, a.b, a.c, b.d,

[sqlite] Ideas or Guide on SQLite Search Engine for a relational database?

I apologize, I sent this from a different email than I registered accidentally. Hi Everyone! The Ask and what I’ve done: I'm building a research database with an embedded SQLite DB using Intellij for development. I've created the data entry point for the users; however, I'm looking for anything