Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

Simon Slavin, on Thursday, October 10, 2019 04:12 PM, wrote... > > On 10 Oct 2019, at 9:03pm, Jose Isaias Cabrera, on > > > 2. The normal SQlite snapshots plus a series of libraries and functions that > can easily be compiled with the original light SQLite. > > Here's the simple way to start the

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

beauty. Learn to see it! Roman From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of Jose Isaias Cabrera [jic...@outlook.com] Sent: Thursday, October 10, 2019 4:03 PM To: SQLite mailing list Subject: [sqlite] SQLite plus the work

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

On 10 Oct 2019, at 9:03pm, Jose Isaias Cabrera wrote: > 2. The normal SQlite snapshots plus a series of libraries and functions that > can easily be compiled with the original light SQLite. Here's the simple way to start the project without breaking anything. Believers in SQLHeavy (or

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

It would be very useful (for me anyway :-) if SQLite followed the Postgres way of being able to install extensions - so for things like Spatialite it would be more embedded than stuck on the side... Retain the core "lite" DBMS but better facilitate being able to expand the functionality.

[sqlite] SQLite plus the works (was Re: Opposite of SQLite)

Simon Slavin, on Thursday, October 10, 2019 03:42 PM, wrote... > > On 10 Oct 2019, at 7:55pm, Ned Fleming, on > > > SQLessLite > > SQDietStartsMonday All kidding aside, and naming continuing, :-), I believe the world will be a happier place with: 1. The normal SQLite snapshots (just like it's

Re: [sqlite] sqlite database changes not committed immediately

fact that there's a Highway to Hell but only a Stairway to Heaven says > a lot about anticipated traffic volume. > > >-Original Message- > >From: sqlite-users On > >Behalf Of Wintech Tech > >Sent: Thursday, 3 October, 2019 04:06 > >To: sqlite-users@mailin

Re: [sqlite] sqlite database changes not committed immediately

-users On >Behalf Of Wintech Tech >Sent: Thursday, 3 October, 2019 04:06 >To: sqlite-users@mailinglists.sqlite.org >Subject: [sqlite] sqlite database changes not committed immediately > >Hi everyone , > >i have posted below Questions on other forums , Please help me solve

[sqlite] sqlite database changes not committed immediately

Hi everyone , i have posted below Questions on other forums , Please help me solve this System.Data.SQLite error . (both are same errors) https://dba.stackexchange.com/questions/249902/sqlite-database-changes-not-commited-immediately

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

Thank you for the recommendations and latest adjustment, both work to resolve the issue. On Fri, Sep 27, 2019 at 12:37 PM Richard Hipp wrote: > On 9/27/19, Micah Moore wrote: > > Hello, > > > > Attempting to use the Pre-release snapshot of SQLite 3.30.0 amalgamation > in > > a [Catalyst]( > >

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

On 9/27/19, Micah Moore wrote: > Hello, > > Attempting to use the Pre-release snapshot of SQLite 3.30.0 amalgamation in > a [Catalyst]( > https://developer.apple.com/ipad-apps-for-mac/) based project -- targeting > UIKit for macOS -- fails with the error "'gethostuuid' is unavailable: not >

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

Hello, Attempting to use the Pre-release snapshot of SQLite 3.30.0 amalgamation in a [Catalyst]( https://developer.apple.com/ipad-apps-for-mac/) based project -- targeting UIKit for macOS -- fails with the error "'gethostuuid' is unavailable: not available on macCatalyst" Adapting this

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

On 9/26/19, Raitses, Alex wrote: > Hello, > I have noticed that security CVE > (https://nvd.nist.gov/vuln/detail/CVE-2019-16168) has been submitted on > SQLite. As far as I can see the patch was submitted to the trunk. > Will CVE patch be included in the 3.30.0? Yes.

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

Of Richard Hipp Sent: Thursday, September 26, 2019 9:26 PM To: General Discussion of SQLite Database ; sqlite-dev Subject: [sqlite] SQLite version 3.30.0 in about two weeks. Our plan is to release SQLite version 3.30.0 in about two weeks - on or about 2019-10-10. Please review the change log

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

"Still says" due to 3_30_0.html is in a draft, I would assume. On Thu, Sep 26, 2019 at 3:31 PM Olivier Mascia wrote: > > Le 26 sept. 2019 à 20:26, Richard Hipp a écrit : > > > > Our plan is to release SQLite version 3.30.0 in about two weeks - on > > or about 2019-10-10. Please review the

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

> Le 26 sept. 2019 à 20:26, Richard Hipp a écrit : > > Our plan is to release SQLite version 3.30.0 in about two weeks - on > or about 2019-10-10. Please review the change log > >https://www.sqlite.org/draft/releaselog/3_30_0.html > > And perhaps download, build, and test the latest

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

, September 26, 2019 2:26 PM To: General Discussion of SQLite Database ; sqlite-dev Subject: [sqlite] SQLite version 3.30.0 in about two weeks. Our plan is to release SQLite version 3.30.0 in about two weeks - on or about 2019-10-10. Please review the change log https://www.sqlite.org

[sqlite] SQLite version 3.30.0 in about two weeks.

Our plan is to release SQLite version 3.30.0 in about two weeks - on or about 2019-10-10. Please review the change log https://www.sqlite.org/draft/releaselog/3_30_0.html And perhaps download, build, and test the latest snapshot. Please let us know if you encounter any problems or

Re: [sqlite] SQLite - macOS

> On Sep 23, 2019, at 9:53 AM, Pierre Clouthier > wrote: > > sqlite3_exec("PRAGMA encoding = \"UTF-8\";") That isn't necessary. SQLite defaults to UTF-8. In most cases SQLite doesn't interpret the byte sequences in a string. It just knows it's using an 8-bit character set and leaves it

Re: [sqlite] SQLite - macOS

> On Sep 23, 2019, at 1:25 PM, Simon Slavin wrote: > >> On 23 Sep 2019, at 5:53pm, Pierre Clouthier >> wrote: >> >> Can anyone explain how to write UTF-8 in SQLite on the Mac? >> >> We use this statement: >> >> sqlite3_exec("PRAGMA encoding = \"UTF-8\";") > > This is not a SQLite

Re: [sqlite] SQLite - macOS

Hi, On Mon, Sep 23, 2019 at 11:58 AM Pierre Clouthier wrote: > > Can anyone explain how to write UTF-8 in SQLite on the Mac? > > We use this statement: > > sqlite3_exec("PRAGMA encoding = \"UTF-8\";") You should probably use this inside #ifdef _WINDOWS #endif Thank you. > > This

Re: [sqlite] SQLite - macOS

On 23 Sep 2019, at 5:53pm, Pierre Clouthier wrote: > Can anyone explain how to write UTF-8 in SQLite on the Mac? > > We use this statement: > > sqlite3_exec("PRAGMA encoding = \"UTF-8\";") This is not a SQLite problem, but a problem with escaping the quotes in language you're using to

Re: [sqlite] SQLite - macOS

Not sure what you code is doing, and you aren’t showing how you are getting your 'é' into SQLite, but U+FFFD is the standard character for malformed data, so something somewhere is complaining about converting something into UTF-8. Also, you CAN’T have a UTF-8 value like 0xC3A9, as that is not

[sqlite] SQLite - macOS

Can anyone explain how to write UTF-8 in SQLite on the Mac? We use this statement: sqlite3_exec("PRAGMA encoding = \"UTF-8\";") This works fine on Windows, but on macOS the data is not being stored correctly. The data to be written (passed to SQLite), is formatted in UTF-8. For

[sqlite] sqlite-tools-win64-x64-3290000.zip missing

Dear Woman and Man! sqlite-tools-win64-x64-329.zip are missing. How to solve this problem? With kind Greetings! ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLITE and the memory

The answer: I remember : I have 256 databases. I have an array of 256 columns into which I store the number of record created. When I insert a record into a table, the corresponding entry into this array is incremented by one. When this element is equal to 1000 I commit the transaction. Not all

Re: [sqlite] SQLITE and the memory

ident Private Bytes) in its display. -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-Original Message- >From: sqlite-users On Behalf >Of Jens Alfke >Sent: Monday, 9 September, 2019 16:18 >To: SQLite mailing

Re: [sqlite] SQLITE and the memory

> On Sep 8, 2019, at 2:12 PM, Philippe RIO <51...@protonmail.ch> wrote: > > I use the windows task manager to see how the memory is used I don't use Windows, but I know that in any modern OS, memory usage is a very vague thing and is tricky to measure. There are quite a few numbers that mean

Re: [sqlite] SQLITE and the memory

> Le 8 sept. 2019 à 23:12, Philippe RIO <51...@protonmail.ch> a écrit : > > Opening the 256 tables : > sqlite3_open_v2(_lpszTbl,[__iTableNumber],SQLITE_OPEN_READWRITE|SQLITE_OPEN_FULLMUTEX,NULL); Wouldn't you be confusing database tables and files? — Best Regards, Meilleures salutations, Met

Re: [sqlite] SQLITE and the memory

t: Sunday, 8 September, 2019 15:13 >To: sqlite-users@mailinglists.sqlite.org >Subject: Re: [sqlite] SQLITE and the memory > >I use the windows task manager to see how the memory is used > > >Opening the 256 tables : >sqlite3_open_v2(_lpszTbl,[__iTableNumber],SQLITE_OPEN_RE

Re: [sqlite] SQLITE and the memory

I use the windows task manager to see how the memory is used Opening the 256 tables : sqlite3_open_v2(_lpszTbl,[__iTableNumber],SQLITE_OPEN_READWRITE|SQLITE_OPEN_FULLMUTEX,NULL); - Kenavo https://md5finder.blogspot.com/ (Never be pleased, always improve) -- Sent from:

Re: [sqlite] SQLITE and the memory

Philippe RIO <51...@protonmail.ch> wrote: > Hello, > I have an application composed of 256 databases. Each database occupied 42Mb > for more than 950 000 records into. > > [samedi 7 septembre 2019 13:11:45] : Number of passwords stored : 244 152 > 645 > [samedi 7 septembre 2019 13:19:28] :

Re: [sqlite] SQLITE and the memory

On 8 Sep 2019, at 2:06pm, Philippe RIO <51...@protonmail.ch> wrote: > These 42Mb are measured after a Vacuum. > When I lauched my application it only opens the databases (all) and the > memory is filled by 57mb just for SQLITE ! How are you opening these database ? Do you have 256 connections,

[sqlite] SQLITE and the memory

Hello, I have an application composed of 256 databases. Each database occupied 42Mb for more than 950 000 records into. [samedi 7 septembre 2019 13:11:45] : Number of passwords stored : 244 152 645 [samedi 7 septembre 2019 13:19:28] : Closing Log file [samedi 7 septembre 2019 13:19:28] : *** Log

Re: [sqlite] sqlite: see: encryption

> On Sep 2, 2019, at 11:41 PM, Vadiraj Villivalam > wrote: > > With the open os like android providing keystore and key generation > mechanism, we want to switch to this secure key generation mechanism and > avoid generating key ourselves. As the key store does not allow the key > itself to

Re: [sqlite] sqlite: see: encryption

On Tue, 3 Sep 2019 12:11:32 +0530, Vadiraj Villivalam wrote: > Hi, > > Our client software uses sqlite for persistence and db is currently > encrypted by passing a app generated key to SEE. > With the open os like android providing keystore and key generation > mechanism, we want to switch to

Re: [sqlite] sqlite: see: encryption

On 3 Sep 2019, at 7:41am, Vadiraj Villivalam wrote: > As the key store does not allow the key > itself to be exported out, I would like to know if sqlite has a mechanism to > leverage the key store way of en/decrypting it (could be with a callback > implemented by app that interfaces with

[sqlite] sqlite: see: encryption

Hi, Our client software uses sqlite for persistence and db is currently encrypted by passing a app generated key to SEE. With the open os like android providing keystore and key generation mechanism, we want to switch to this secure key generation mechanism and avoid generating key ourselves. As

[sqlite] SQLite vulns

On 27 Aug 2019, at 9:40pm, Jens Alfke wrote: > My question was simply whether SQLite itself is considered safe when > operating on an untrusted database file. A worthwhile question which I discussed a little in an earlier post. The SQLite devs take this question extremely seriously. SQLite

Re: [sqlite] SQLite Encryption Extension For Use with With PHP 7.x Code

On 20 Aug 2019, at 8:40pm, Mark Tomlin wrote: > I found the regular sqlite3::open method has an $encryption_key parameter. > > https://www.php.net/manual/en/sqlite3.open.php Yep. > As I am using PDO for the interface into SQLite, I wonder if there is a > similar parameter for that interface.

Re: [sqlite] SQLite Encryption Extension For Use with With PHP 7.x Code

On 8/20/19, Mark Tomlin wrote: > I've looked at the PRAGMA statements and there doesn't appear to > be any public documentation on this interface. The PRAGMAs in question are part of the SEE documentation, as they are unique to SEE. -- D. Richard Hipp d...@sqlite.org

Re: [sqlite] SQLite Encryption Extension For Use with With PHP 7.x Code

Thank you Richard for the extremely quick response. I found the regular sqlite3::open method has an $encryption_key parameter. https://www.php.net/manual/en/sqlite3.open.php As I am using PDO for the interface into SQLite, I wonder if there is a similar parameter for that interface. Perhaps

Re: [sqlite] SQLite Encryption Extension For Use with With PHP 7.x Code

On 8/20/19, Mark Tomlin wrote: > I would like to use SQLite's Encryption Extension with my PHP 7.2 code > base, as well as 7.3 and 7.4 code bases moving forward. My hope is is that > the see-sqlite.c code file can be simply renaming it to sqlite.c and > dropping it into PHP's build directory.Then

[sqlite] SQLite Encryption Extension For Use with With PHP 7.x Code

I would like to use SQLite's Encryption Extension with my PHP 7.2 code base, as well as 7.3 and 7.4 code bases moving forward. My hope is is that the see-sqlite.c code file can be simply renaming it to sqlite.c and dropping it into PHP's build directory.Then compiling it as I normally would. I'm

[sqlite] SQLITE with Kotlin

Hi Guys I want to write an application in kotlin which uses SQLITE. Is there already a good Kotlin package which provides SQLITE services (I know that there is one for Android development, but I’m not developing on top of Android) Thanks ___

Re: [sqlite] SQLITE Return Exponential value in the latest version(3.28.0) rather than integer number .

Hi Bhavesh, This is a common thing with 3rd party systems and engines (like SQlite) etc. One day, you made a simple query which did not specify the output specifically (or the format, or the order, or such), BUT you liked the output as it was on that day, and then possibly made your program

[sqlite] SQLITE Return Exponential value in the latest version(3.28.0) rather than integer number .

Hello SQLite Community Members, I am facing an issue with SQLite latest version(3.28.0). SQLITE Return Exponential value in the latest version(3.28.0) rather than integer number . The old version (3.6.2) return the same integer value which is inserted . Below is the screenshots of my

Re: [sqlite] sqlite-users Digest, Vol 138, Issue 4

On Tue, 4 Jun 2019 11:26:12 -0700 "Doug" wrote: > select songfile_id,dancename,dancegroupname from songfiletable where > dancename like "Waltz"; What Shawn Wagner's answer shows you is that 'Waltz' is a string and "Waltz" is a column name, because in SQL double-quotes

Re: [sqlite] sqlite-users Digest, Vol 138, Issue 4

Throwing a wild idea out: Can you try using single-quotes (e.g. "...where dancename = 'Waltz'..."). Single-quotes are meant to be used for text-literals; double-quotes are meant to "protect" field/table names where they clash with keywords (or contain "odd" characters). Additionally, do you by any

Re: [sqlite] sqlite-users Digest, Vol 138, Issue 4

rdo de Paula) > >2. select * where abc like "xxx" works,...where abc='xxx' > > fails > > (Doug) > >3. Re: select * where abc like "xxx" works, ...where abc='xxx' > > fails (Simon Slavin) > >4. Re: select * where abc like "xxx" works,

Re: [sqlite] sqlite-users Digest, Vol 138, Issue 4

gt;5. Re: Bug in sqlite3.c (bhandari_nikhil) > > > -- > > > Message: 1 > Date: Sun, 2 Jun 2019 11:15:35 -0300 > From: Carlos Eduardo de Paula > To: dcla...@blastwave.org, "sqlite-users@mailin

Re: [sqlite] sqlite-users Digest, Vol 138, Issue 4

> ---- > > Message: 1 > Date: Sun, 2 Jun 2019 11:15:35 -0300 > From: Carlos Eduardo de Paula > To: dcla...@blastwave.org, "sqlite-users@mailinglists.sqlite.org" > > Subject: Re: [sqlite] SQLite build on Risc-V > Message-ID

Re: [sqlite] SQLite build on Risc-V

I'm on a SiFive Unleashed board running Debian Linux on Kernel 4.19. -- Sent from IPhone ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite build on Risc-V

On 5/31/19 11:04 AM, Carlos Eduardo de Paula wrote: I tried to build SQLite from sources on Risc-V architecture but the ./configure script fails. Replacing config.guess and config.sub with the ones from automake 1.16 package fixes the problem and SQLite builds successfully. Carlos What

[sqlite] SQLite build on Risc-V

I tried to build SQLite from sources on Risc-V architecture but the ./configure script fails. Replacing config.guess and config.sub with the ones from automake 1.16 package fixes the problem and SQLite builds successfully. Carlos -- *Carlos Eduardo de

Re: [sqlite] SQLite with single writer on Windows network share

Andrew Moss, on Monday, May 13, 2019 04:59 AM, wrote... >Many thanks for all your comments and suggestions. I will bear it all in >mind. Are you trying to shut us up? :-) ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] SQLite with single writer on Windows network share

Many thanks for all your comments and suggestions. I will bear it all in mind. On Sun, 12 May 2019 at 12:26, Warren Young wrote: > On May 11, 2019, at 5:52 PM, Jose Isaias Cabrera > wrote: > > > > Warren Young, on Saturday, May 11, 2019 06:20 PM, wrote... > >> > >> On May 11, 2019, at 4:10 PM,

Re: [sqlite] SQLite with single writer on Windows network share

On May 11, 2019, at 5:52 PM, Jose Isaias Cabrera wrote: > > Warren Young, on Saturday, May 11, 2019 06:20 PM, wrote... >> >> On May 11, 2019, at 4:10 PM, Thomas Kurz wrote: >> >> It should run under Cygwin and WSL. > > I tried to build it. I fould out that I needed brew Cygwin’s own package

Re: [sqlite] SQLite with single writer on Windows network share

qlite.org] On Behalf Of Simon Slavin >Sent: Saturday, 11 May, 2019 18:04 >To: SQLite mailing list >Subject: Re: [sqlite] SQLite with single writer on Windows network >share > >On 12 May 2019, at 12:52am, Jose Isaias Cabrera >wrote: > >> the other question is, that I think

Re: [sqlite] SQLite with single writer on Windows network share

On 12 May 2019, at 12:52am, Jose Isaias Cabrera wrote: > the other question is, that I think I only need the gcc@6 package to build > Bedrockdb. Does anybody know what is gcc@6? But I don't know where to find it for your platform.

Re: [sqlite] SQLite with single writer on Windows network share

Warren Young, on Saturday, May 11, 2019 06:20 PM, wrote... > >On May 11, 2019, at 4:10 PM, Thomas Kurz wrote: > > It should run under Cygwin and WSL. > > I doubt it’s any more difficult to port to Windows than dozens of other > similar > packages like Apache and MySQL. Someone’s just got to

Re: [sqlite] SQLite with single writer on Windows network share

On 11 May 2019, at 11:20pm, Warren Young wrote: > I doubt it’s any more difficult to port to Windows than dozens of other > similar packages like Apache and MySQL. Mutex/Locking. You're relying on a File System and/or a Network File System that does locking properly. I'm not saying that

Re: [sqlite] SQLite with single writer on Windows network share

On May 11, 2019, at 4:10 PM, Thomas Kurz wrote: > >> How about you give up on the idea of using Windows shares to distribute a >> SQLite DB and use a tool meant for the job, such as BedrockDB? > > BedrockDB is recommended here now and then, and it sounds interesting indeed. > However, it's

Re: [sqlite] SQLite with single writer on Windows network share

> How about you give up on the idea of using Windows shares to distribute a > SQLite DB and use a tool meant for the job, such as BedrockDB? BedrockDB is recommended here now and then, and it sounds interesting indeed. However, it's not available for Windows. (This should always be noted when

Re: [sqlite] SQLite with single writer on Windows network share

On Fri, May 10, 2019 at 4:40 AM Warren Young wrote: > Bedrock is based in part on the Paxos algorithm, another major advance in > distributed computing, and another of Leslie Lamport’s brainchildren: > > https://en.wikipedia.org/wiki/Paxos_(computer_science) In the same vein, there's also

Re: [sqlite] SQLite with single writer on Windows network share

On May 9, 2019, at 4:56 PM, James K. Lowden wrote: > > file I/O operations act on the kernel’s filebuffer It’s more widely called a buffer cache or page cache: https://en.wikipedia.org/wiki/Page_cache > If this sounds like an indictment of NFS, it's really not. In large part, it’s a

Re: [sqlite] SQLite with single writer on Windows network share

On Wed, 8 May 2019 21:36:43 +0200 Clemens Ladisch wrote: > Andrew Moss wrote: > > ... an SQLite database hosted on a windows network share (using > > server 2012 R2 or later). We are well aware this is not advisable > > There are three possible sources of network filesystem data > corruption: >

Re: [sqlite] SQLite with single writer on Windows network share

Andrew Moss wrote: > ... an SQLite database hosted on a windows network share (using server > 2012 R2 or later). We are well aware this is not advisable There are three possible sources of network filesystem data corruption: 1) Bad locking implementations. Some Unix-y network filesystems

Re: [sqlite] SQLite with single writer on Windows network share

Simon Slavin wrote: > setting the journal mode of the database to WAL will ... certainly lead to data corruption; WAL requires shared memory, which cannot work over a network filesystem. Regards, Clemens ___ sqlite-users mailing list

Re: [sqlite] SQLite with single writer on Windows network share

On May 8, 2019, at 10:30 AM, Jose Isaias Cabrera wrote: > > Warren Young, on Wednesday, May 8, 2019 12:10 PM, wrote... > >> How about you give up on the idea of using Windows shares to distribute a >> SQLite DB >> and use a tool meant for the job, such as BedrockDB? >> >>

Re: [sqlite] SQLite with single writer on Windows network share

Warren Young, on Wednesday, May 8, 2019 12:10 PM, wrote... >On May 8, 2019, at 8:42 AM, Andrew Moss wrote: >How about you give up on the idea of using Windows shares to distribute a >SQLite DB > and use a tool meant for the job, such as BedrockDB? > >https://bedrockdb.com/ Man, I wish this

Re: [sqlite] SQLite with single writer on Windows network share

On May 8, 2019, at 8:42 AM, Andrew Moss wrote: > > We are currently backed into a corner by a customer In what way, exactly? It might help to know. > and are looking at > using an SQLite database hosted on a windows network share (using server > 2012 R2 or later). You’ve fallen victim to the

Re: [sqlite] SQLite with single writer on Windows network share

On 8 May 2019, at 3:42pm, Andrew Moss wrote: > My question is, if we limit the application (through other means) to a > single writer, but allow multiple readers, does that remove the risk of > database corruption from multiple SQLite processes? > > Any notes from other users who had to do

Re: [sqlite] SQLite with single writer on Windows network share

Andrew Moss, on Wednesday, May 8, 2019 10:42 AM, wrote... >We are currently backed into a corner by a customer and are looking at >using an SQLite database hosted on a windows network share (using server >2012 R2 or later). We are well aware this is not advisable and have read

[sqlite] SQLite with single writer on Windows network share

Hi, We are currently backed into a corner by a customer and are looking at using an SQLite database hosted on a windows network share (using server 2012 R2 or later). We are well aware this is not advisable and have read https://www.sqlite.org/whentouse.html. My question is, if we limit the

Re: [sqlite] SQLite windows function support

On 5/3/19, Chien-Chih Yu wrote: > Since all current window functions are "draft version"... I'm not sure were you are getting this information. See https://www.sqlite.org/windowfunctions.html for the official documentation. Ahead of each release, we always publish advance copies of the new

[sqlite] SQLite windows function support

To whom it may concern We are evaluating the use of SQLite window functions. Since all current window functions are "draft version", we would like to know when these window functions will become stable version. Thanks Chien-Chih Yu This email and any attachments are intended for the sole use of

Re: [sqlite] SQLite error while fetching the data from a table

Hi All, Hi Ananta Need quick help to resolve one issue i am getting now. I am a new user of SQLite. my code: connection = DriverManager.getConnection("jdbc:sqlite:C:\\sqllite\\sqlite-tools-win32-x86-328\\Stories.db"); Statement st = connection.createStatement(); ResultSet b =

Re: [sqlite] SQLite error while fetching the data from a table

On 22-4-2019 14:03, Ananta Jena wrote: Hi All, Need quick help to resolve one issue i am getting now. I am a new user of SQLite. my code: connection = DriverManager.getConnection("jdbc:sqlite:C:\\sqllite\\sqlite-tools-win32-x86-328\\Stories.db"); Statement st =

[sqlite] SQLite error while fetching the data from a table

Hi All, Need quick help to resolve one issue i am getting now. I am a new user of SQLite. my code: connection = DriverManager.getConnection("jdbc:sqlite:C:\\sqllite\\sqlite-tools-win32-x86-328\\Stories.db"); Statement st = connection.createStatement(); ResultSet b = st.executeQuery("select

Re: [sqlite] SQLite v3.27.2 memory usage

On Apr 14, 2019, at 10:18 PM, David Ashman - Zone 7 Engineering, LLC wrote: > > It appears that there is a leak somewhere. It is certainly in your code. My bet’s on a missing sqlite3_finalize() call, but there are many other possibilities. > Does anyone know why this error occurs? I

[sqlite] SQLite v3.27.2 memory usage

Hello - I have a question on SQLite memory usage. I'm successfully using SQLite v3.27.2 amalgamation on an embedded ARM processor from STMicro with SD card and no OS.  The database file size is about 3.8GB.  The file system is Segger emFile FAT32.  I've configured SQLite to use 3.7MB RAM for

Re: [sqlite] SQLite version 3.28.0 beta 1

I would really support this other approach. It seems more extensible and eventually would address on of my pain points in SQLite, not knowing what type of statement is being executed. -- Sent from: http://sqlite.1065341.n5.nabble.com/ ___

Re: [sqlite] SQLite version 3.28.0 beta 1

Rather than sqlite3_stmt_isexplain(S) would it be possible to define a sqlite3_stmt_type(S) function instead ? This would return integers equivalent to SQLITE_STMT_ERROR = -1 SQLITE_STMT_OTHER = 0 SQLITE_STMT_EXPLAIN = 1 and in future other values as they become useful ? You could add

[sqlite] sqlite bug report

Summary Alter table rename to fails if the database contains a view which selects from a nonexistent table. Seen on sqlite 3.27.2. Script to reproduce it: create view view_1 as select * from table_1; create table table_2 (col_1 text, col_2 text); alter table table_2 rename to table_3; The

[sqlite] SQLite version 3.28.0 beta 1

The current "Prerelease Snapshot" at https://sqlite.org/download.html is considered a beta. We expect bug fixes only from now until the official release of version 3.28.0. If you can, please download the beta and try it out in your application(s). Report any problems and/or performance

Re: [sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE field IN (list, of, items)

On 2/19/19, Richard Hipp wrote: > > I have checked in a fix on trunk > (https://www.sqlite.org/src/info/b5f90bfe6295ab3a) but the ticket > (https://www.sqlite.org/src/info/df46dfb631f75694) has been kept open > pending further testing and analysis. Further testing and analysis lead to a better

Re: [sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE field IN (list, of, items)

On 2/19/19, Ignacio Losiggio wrote: > > CREATE TABLE IF NOT EXISTS t (id integer NOT NULL PRIMARY KEY > AUTOINCREMENT); > INSERT INTO t VALUES(1); > SELECT a.id FROM t AS a INNER JOIN t as b ON a.id = b.id WHERE a.id IN > (1, 2, 3); I have checked in a fix on trunk

Re: [sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE fieldIN (list, of, items)

... > To: SQLite mailing list > Subject: Re: [sqlite] sqlite segfault on INNER JOIN ON (...) > + WHERE fieldIN (list, of, items) > > > If you compile with assert() statements enabled (using the > --enable-debug option with ./configure or otherwise adding the > -DSQL

Re: [sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE fieldIN (list, of, items)

Additional background: The optimization that caused this bug was an attempt to fix a performance regression reported here (https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg113314.html) which was in turned caused by a fix to a prior bug here

Re: [sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE fieldIN (list, of, items)

Further debugging hints (for those who are interested): If you compile with --enable-debug and run the script below, it will give you more information about what is going on in the bytecode: CREATE TABLE IF NOT EXISTS t1(id INTEGER PRIMARY KEY); INSERT INTO t1 VALUES(1); .eqp trace SELECT a.id

Re: [sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE fieldIN (list, of, items)

If you compile with assert() statements enabled (using the --enable-debug option with ./configure or otherwise adding the -DSQLITE_DEBUG flag) then you will hit an assertion fault earlier. The problem is that the same ephemeral table - the in-memory table that is constructed to hold the RHS of the

Re: [sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE fieldIN (list, of, items)

> Wow; can confirm. I crashed it in my debugger in the > amalgamation of 3.27.1 > in the function SQLITE_PRIVATE RecordCompare > sqlite3VdbeFindCompare(UnpackedRecord *p) > > At line 80720, if( p->pKeyInfo->nAllField<=13 ) > > in that case: > pKeyInfo is NULL Lastly, if it helps, converting

Re: [sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE field IN (list, of, items)

> -Original Message- > From: sqlite-users > [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On > Behalf Of Ignacio Losiggio > Sent: Tuesday, February 19, 2019 6:27 PM > To: sqlite-users@mailinglists.sqlite.org > Subject: [sqlite] sqlite segfault on INNER JOI

[sqlite] sqlite segfault on INNER JOIN ON (...) + WHERE field IN (list, of, items)

(I'm sorry if my description of the bug is not good. I tried to get as much information possible before sending this email). A few days ago I encountered some weird segfaults on my django application. After a bit of troubleshooting I realized that the applications was crashing on the sqlite

Re: [sqlite] sqlite 3.37.1: void function returns value

Dominique, what I said was that it is undefined behaviour in C++ to return a *value* in a void function. That is still true. On Mon, Feb 11, 2019 at 2:49 PM Dominique Devienne wrote: > On Mon, Feb 11, 2019 at 1:11 PM Clemens Ladisch > wrote: > > > Peter da Silva wrote: > > > I am pretty sure

Re: [sqlite] sqlite 3.37.1: void function returns value

On Mon, Feb 11, 2019 at 1:11 PM Clemens Ladisch wrote: > Peter da Silva wrote: > > I am pretty sure that the code is not legal C > > Indeed; C99 and C11 say in 6.3.2.2: > | The (nonexistent) value of a void expression (an expression that has > | type void) shall not be used in any way [...] >

Re: [sqlite] sqlite 3.37.1: void function returns value

Peter da Silva wrote: > I am pretty sure that the code is not legal C Indeed; C99 and C11 say in 6.3.2.2: | The (nonexistent) value of a void expression (an expression that has | type void) shall not be used in any way [...] and in 6.8.6.4: | A return statement with an expression shall not appear

Re: [sqlite] sqlite 3.37.1: void function returns value

> On Feb 11, 2019, at 6:33 AM, Peter da Silva wrote: > > I am pretty sure that the code is not legal C because it's using the return > value of a void function, as well as returning a value from a void > function. Compilers that "do what I mean" and accept it are in error. It's > certainly

Re: [sqlite] sqlite 3.37.1: void function returns value

I am pretty sure that the code is not legal C because it's using the return value of a void function, as well as returning a value from a void function. Compilers that "do what I mean" and accept it are in error. It's certainly possible that some obscure clause in some C standard blesses it but I

Re: [sqlite] sqlite 3.37.1: void function returns value

I'm using cl.exe v19.12. To summarize: SQLite 3.24 compiles fine with warning as error enabled with cl.exe v19.12 SQLite 3.27.1 does not compile with warning as error enabled with cl.exe v19.12. To me, it looks like a simple fix to avoid writing "return " in void functions even if is a void

<    1   2   3   4   5   6   7   8   9   10   >