On Mon, Nov 23, 2015 at 7:00 PM, wrote:
>
>
>
> Maybe there's a technical reason that this functionality wasn't added to
> SQLite. Does anyone know?
>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sql
Maybe there's a technical reason that this functionality wasn't added to
SQLite. Does anyone know?
On 23/11/2015 11:32 AM, Rowan Worth wrote:
> Hi Bruce,
>
> I had a go at post-processing the sqlite3 shell's output to apply thousand
> separators. I don't recommend looking too hard at the sed for the sake of
> your sanity, but the gist is it repeatedly prepends a comma to trailing
> groups of thr
On 23-11-15 15:23, Richard Hipp wrote:
> On 11/23/15, Johan W. Van Ooijen wrote:
>> On 23-11-15 15:01, Richard Hipp wrote:
>> > Try compiling with -DSQLITE_MEMORY_BARRIER=""
>>
>> This will produce an empty sqlite3MemoryBarrier() function; is such a
>> memory barrier not necessary under 32
On 23-11-15 15:01, Richard Hipp wrote:
> Try compiling with -DSQLITE_MEMORY_BARRIER=""
This will produce an empty sqlite3MemoryBarrier() function; is such a
memory barrier not necessary under 32-bit and/or 64-bit Windows?
Regards,
Johan Van Ooijen
In trying to find a solution to the unresolved external
'__faststorefence' problem I get with the SQLite 3.9.2 amalgamation
under Embarcadero C++Builder XE7, I see that macro SQLITE_OS_WIN is used
on lines 9153 and 9169, whereas SQLITE_OS_WIN becomes #defined after
line 11225. This does not see
On Mon, Nov 23, 2015 at 1:57 PM, Bruce Hohl wrote:
> www.sqlite.org/loadext.html states that: "Loadable extensions are C-code."
> Can someone confirm this please.
>
pedantically speaking: the _entry point_ for the extension is C. The
implementation may be in any language.
> If I figure out so
On 23 Nov 2015, at 1:02pm, Stephan Beal wrote:
> On Mon, Nov 23, 2015 at 1:57 PM, Bruce Hohl wrote:
>
>> www.sqlite.org/loadext.html states that: "Loadable extensions are C-code."
>> Can someone confirm this please.
>
> pedantically speaking: the _entry point_ for the extension is C. The
> im
Hi,
1)
Using v3.8.6 I noticed that journal files were created and removed while
executing a transaction event though I had set the "PRAGMA journal_mode =
MEMORY;".
Right after creating a new sqlite file using sqlite3_open16() I execute a
couple of PRAGMA statements.
Right after executing all
Hi Bruce,
I had a go at post-processing the sqlite3 shell's output to apply thousand
separators. I don't recommend looking too hard at the sed for the sake of
your sanity, but the gist is it repeatedly prepends a comma to trailing
groups of three digits, and then repeatedly removes commas which ap
On Tue, 17 Nov 2015 22:29:10 -0500
Richard Hipp wrote:
> With CHECK, and UNIQUE, and NOT NULL constraints, you do know that the
> constraint has failed right away. And for those constraints, SQLite
> does provide more detail about exactly which constraint failed. But
> for FK constraints, you n
On 11/23/15, Johan W. Van Ooijen wrote:
> On 23-11-15 15:01, Richard Hipp wrote:
> > Try compiling with -DSQLITE_MEMORY_BARRIER=""
>
> This will produce an empty sqlite3MemoryBarrier() function; is such a
> memory barrier not necessary under 32-bit and/or 64-bit Windows?
>
The necessity of a mem
Try compiling with -DSQLITE_MEMORY_BARRIER=""
On 11/23/15, Johan W. Van Ooijen wrote:
> In trying to find a solution to the unresolved external
> '__faststorefence' problem I get with the SQLite 3.9.2 amalgamation
> under Embarcadero C++Builder XE7, I see that macro SQLITE_OS_WIN is used
> on lin
On Sun, Nov 22, 2015 at 8:14 PM, Simon Slavin wrote:
> Of course that too is unlikely to happen, this time for
> backward-compatibility reasons. Maybe it could be a consideration of
> SQLite4.
>
Why keep bringing up SQLite4? AFAIK, SQLite4 has been inactive for a long
time, and not much of a re
On 23 Nov 2015, at 7:56am, Simon Slavin wrote:
> On 23 Nov 2015, at 7:41am, Dominique Devienne wrote:
>
>> Why keep bringing up SQLite4? AFAIK, SQLite4 has been inactive for a long
>> time, and not much of a response anytime someone asks about it.
>
> It's a way of telling people who ask for
Gentlemen, thanks all for your comments. Before I posted I knew the
thousands separator was problematic for the reasons stated by Simon. I
figured it was intentionally left out of sqlite's printf(). I wanted to
make sure I was not missing a known or easy solution.
As sqweek/Mohit suggested I wil
On 23 Nov 2015, at 7:41am, Dominique Devienne wrote:
> On Sun, Nov 22, 2015 at 8:14 PM, Simon Slavin wrote:
>
>> Of course that too is unlikely to happen, this time for
>> backward-compatibility reasons. Maybe it could be a consideration of
>> SQLite4.
>
> Why keep bringing up SQLite4? AFAIK
17 matches
Mail list logo
