[sqlite] Do you mean utf8_fprintf on this commit ?

Hello mistachkin ! On this commit https://www.sqlite.org/src/info/8cf01fff232d15d3 do you mean "utf8_fprintf" instead of "utf8_printf" ? To be consistent with the underling wrapped function ! Cheers !

[sqlite] Fwd: Happy New Year

-- Forwarded message -- From: Igor Korot Date: Thu, Dec 31, 2015 at 5:06 PM Subject: Happy New Year To: "python-list at python.org" , General Discussion of SQLite Database Happy New Year to everybody on those lists. Let this year brings us a lot of

[sqlite] non-integer rowid/document id

Excerpts from jeremy's message of 2015-12-14 11:09:48 -0700: > Hi all, > > I'm working with FTS5 and I'd like to guarantee that a particular document is > indexed only once. I have what I consider to be a document id, but it is not > an > integer value its a hexadecimal string, think

[sqlite] Function patternCompare() not EBCDIC friendly

Roland, thank you VERY much for sharing your findings. Appreciated! I think that the ability to compile SQLite on z/OS out of the box is a great achievement. We'll need to make sure that this will still hold true for future releases. While using your dump procedure allows exchanging

[sqlite] Magic number in sqlite source code

Hello, Richard! Probably PTR_SZ or PAGE_PTR_SZ would be good? I feel confusing about OVFL_. Why size of the pointer to the first overflow page could be different from size of another pointers? Sorry, I'm far from the code and should not discourse. Just have an idea that name should be as common

[sqlite] Do you mean utf8_fprintf on this commit ?

Domingo Alvarez Duarte wrote: > > On this commit https://www.sqlite.org/src/info/8cf01fff232d15d3 do you > mean "utf8_fprintf" instead of "utf8_printf" ? > No, I meant to use the existing "utf8_printf" function (and the new "raw_printf" macro). -- Joe Mistachkin

[sqlite] System.Data.SQLite: Incorrect implementation of SQLiteDataReader::GetSchemaTable()

Hi, The implementation of GetSchemaTable() in SQLiteDataReader seems to be based on the properties of the columns used in the select. Obviously uniqueness, nullness and primary key properties do not transfer when only a subset of the columns is selected or combined with data from other tables.

[sqlite] System.Data.SQLite: Incorrect implementation of SQLiteDataReader::GetSchemaTable()

Jann Roder wrote: > > The implementation of GetSchemaTable() in SQLiteDataReader seems to be > based on the properties of the columns used in the select. Obviously > uniqueness, nullness and primary key properties do not transfer when > only a subset of the columns is selected or combined with

[sqlite] Function patternCompare() not EBCDIC friendly

Roland, Congrads on getting something to work with sqlite and z/OS. ?How did you resolve the file I/O issues, or did you have any. ?I figured sqlite should be able to run on z/OS a few years back due to the portable nature of the code I saw. ? But the?mainframe guys who supposedly knew, told

[sqlite] Magic number in sqlite source code

Hello Duncan ! I saw a very good point on your suggestion ! I'll use it when writing/refactoring code. Thanks a lot ! ? > Wed Dec 30 2015 11:51:54 pm CET CET from "Darren Duncan" > Subject: Re: [sqlite] Magic number in sqlite >source code > > On 2015-12-30 12:51 PM, Richard Hipp

[sqlite] Magic number in sqlite source code

Hello Richard ! Sorry again for the mess with format and missing parameter on the maybe more friendly function "ptrmapPutOvflPtr" ! I decided to really look at the code now (before I looked at the diffs and saw so many magic numbers "4"). I know that what I'm saying here not always

[sqlite] Magic number in sqlite source code

Hello Richard ! !!! Last message got messed format, sorry !!! I decided to really look at the code now (before I looked at the diffs and saw so many magic numbers "4"). I know that what I'm saying here not always I follow for n reasons but thanks for giving me a chance to take a moment and

[sqlite] Magic number in sqlite source code

Hello Richard ! I decided to really look at the code now (before I looked at the diffs and saw so many magic numbers "4"). I know that what I'm saying here not always I follow for n reasons but thanks for giving me a chance to take a moment and reflect on this that do not seem a problem when