On Fri, 6 May 2016 01:56:47 +0300, "Tony Papadimitriou"
wrote:
> Windows!
There's gawk for windows, for this purpose almost the same as
sed. And apart form cygwin, there is a unch of unix utilities
under the name of UnxUtils.
See https://en.wikipedia.org/wiki/UnxUtils
and
Thanks for the suggestions.
The session extension would work, all tables have rowids. The added
flexibility to insert/update into the database copies first
independently of each other is valuable.
Tracing the inserts/updates seems also a good idea, available with the
present Sqlite version.
On 7 May 2016, at 3:28am, Keith Medcalf wrote:
> I presume you mean that running 32-bit application on a 64-bit OS is slower
> than the same application run on a 32-bit OS.
Hold on. The original poster was talking about using a 32-bit DLL, not a
32-bit application. I don't know what
As for the session extension
"https://www.sqlite.org/draft/sessionintro.html;, what I'd like to ask
is when this is more useful than the RBU extension
"http://sqlite.org/rbu.html; ? The two seem to serve a similar
purpose.
Ambrus
Using SQLite 3.12.2 on Windows 10.
Compiled from the amalgation to a 64 bit dll with these compile options:
ENABLE_COLUMN_METADATA=1
SYSTEM_MALLOC=1
THREADSAFE=0
ENABLE_EXPLAIN_COMMENTS=1
When I run sqlite3_compileoption_used the first 3 compile options show
indeed fine as they
should, but
Hi Rob,
I think Clemens suggestion may be worth investigating, in case you do not
want to stop the updates (which probably means a change in your workflow
and some effort at other places anyways).
I think this may work:
- Use WAL, and turn off automatic checkpointing
My apologies if this has already been raised...
When I first read about this I thought (assumed) that 'changes' were meant
to be just data changes, i.e. changes to rows where they have been inserted,
updated and/or deleted. In my experience a fairly typical journaling
function that a number of
> On 7 May 2016, at 3:28am, Keith Medcalf wrote:
> > I presume you mean that running 32-bit application on a 64-bit OS is
> slower than the same application run on a 32-bit OS.
> Hold on. The original poster was talking about using a 32-bit DLL, not a
> 32-bit application. I don't know what
There are reasons for 64bit to be faster - more registers to work with.
(from https://en.wikipedia.org/wiki/X86-64 )
In addition to increasing the size of the general-purpose registers,
the number of named general-purpose registers is increased from eight
(i.e. eax, ebx, ecx, edx, ebp, esp, esi,
Hi Stephan,
On 18 February 2016 at 13:55, Stephan Beal wrote:
> On Thu, Feb 18, 2016 at 10:42 PM, Stephan Beal
> wrote:
>
>> Here we go:
>>
>> http://fossil.wanderinghorse.net/download/cal.sql
>>
>
> sorry, one more: it was just updated with minor doc improvements and better
> syntax conformance
10 matches
Mail list logo