> On Jul 28, 2017, at 2:46 PM, petern wrote:
>
> The attack vector is described well enough. A penetration search harness
> would work directly from predictable accesses to the published key
> constants as mapped into process address space. [Full ASLR decoding, see
> the paper, isn't needed fo
Here I'm replying to Richard and subsequent comments on Richard's question.
The attack vector is described well enough. A penetration search harness
would work directly from predictable accesses to the published key
constants as mapped into process address space. [Full ASLR decoding, see
the pap
Am Thu, 27 Jul 2017 16:47:00 -0700 schrieb Jens Alfke:
> The project I work on needs the ability to do Unicode-savvy string
> collation, which SQLite doesn’t provide. But we’re somewhat sensitive to
> code size, so we don’t want to just drop in the hugeness that is ICU.
> We’ve looked at a couple
On 28 Jul 2017, at 12:47am, Jens Alfke wrote:
> The project I work on needs the ability to do Unicode-savvy string collation,
> which SQLite doesn’t provide. But we’re somewhat sensitive to code size, so
> we don’t want to just drop in the hugeness that is ICU. We’ve looked at a
> couple of ot
I would also love to know the answer to this.
On Thu, Jul 27, 2017 at 5:47 PM, Jens Alfke wrote:
> The project I work on needs the ability to do Unicode-savvy string
> collation, which SQLite doesn’t provide. But we’re somewhat sensitive to
> code size, so we don’t want to just drop in the hugen
On 7/28/17, Rob Richardson wrote:
> I have a program reads data from 17 PLCs and writes it into SQLite databases
> every minutes. Every midnight, it deletes old data and vacuums the
> databases. It's behaving strangely after that. I think the problem begins
> because the vacuum operation is sti
I have a program reads data from 17 PLCs and writes it into SQLite databases
every minutes. Every midnight, it deletes old data and vacuums the databases.
It's behaving strangely after that. I think the problem begins because the
vacuum operation is still going on at 12:01, when the next read
I believe, a closing parenthesis should be before the final comma in
this line:
http://www.sqlite.org/src/artifact/0e2603c23f0747c5?ln=4202
Ralf
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/
8 matches
Mail list logo