On 2016/01/24 10:15 PM, audio muze wrote:
> I have a large table with ~350k records for which I'm in the process of
> standardising data.
350k records is not exactly a "large" table, A table scan would complete
in a couple of seconds on a normal system. 350 million rows are more
substantial
Teg,
On Mon, Jan 25, 2016 at 9:25 PM, Igor Korot wrote:
> Hi, Teg,
>
> On Mon, Jan 25, 2016 at 5:21 PM, Igor Korot wrote:
>> Hi, Teg,
>>
>> On Mon, Jan 25, 2016 at 4:51 PM, Teg wrote:
>>> Hello Igor,
>>>
>>> Then I'd note the address of the object (make a copy of the pointer
>>> right as
On Sun, 24 Jan 2016 21:26:41 +
Bart Smissaert wrote:
> http://www.cdecl.org/
>
> It doesn't work though with complex arguments like this:
> void (*xFunc)(sqlite3_context*,int,sqlite3_value**)
In isolation, that's a syntax error because e.g. sqlite3_value is not
defined (on that line,
Hi, Teg,
On Mon, Jan 25, 2016 at 5:21 PM, Igor Korot wrote:
> Hi, Teg,
>
> On Mon, Jan 25, 2016 at 4:51 PM, Teg wrote:
>> Hello Igor,
>>
>> Then I'd note the address of the object (make a copy of the pointer
>> right as it's allocated) and then verify that the address you're
>>
anyone?
On 2016/01/25 7:02 PM, Bernard McNeill wrote:
> Hello,
>
> Anyone with any experiences with this (good or bad)?
>
> Idea to have Sqlite database on server, accessed from a few ultra-thin
> Terminal clients.
Terminal clients? You mean the kind where the terminal client is
basically just
On 25 Jan 2016, at 5:02pm, Bernard McNeill wrote:
> Idea to have Sqlite database on server, accessed from a few ultra-thin
> Terminal clients.
SQLite is not a server/client system. You would have to write your own
server/client system.
Simon.
On 2016/01/25 5:08 PM, Matthias-Christian Ott wrote:
> On 25/01/16 14:14, Richard Hipp wrote:
>> On 1/19/16, Meinlschmidt Stefan wrote:
>>> Shutting down power right after a successfully committed
>>> transaction rolls back that transaction on next startup.
>> Patches checked in:
>>
>>
Hello,
What is the difference between the dll included in:
http://sqlite.org/2015/sqlite-dll-win64-x64-3090200.zip
And the one included in:
http://sqlite.org/2016/sqlite-uap-3100200.vsix Redist/Retail/x64/sqlite3.dll
?
The first one works with libffi, the second doesn't.
Is there a
On 2016-01-25 16:47, Richard Hipp wrote:
> On 1/25/16, Matthias-Christian Ott wrote:
>>
>> Does this mean that if I use SQLite SQLITE_EXTRA_DURABLE=0, PRAGMA
>> journal_mode=DELETE and PRAGMA synchronous=FULL, SQLite could loose a
>> transaction that it said to be committed depending on the VFS?
Igor Korot wrote:
> The DLL where SQLite pointer is alocated there is a DLLMain.
And what does it do?
> BOOL APIENTRY DLLMain()
> {
> }
Is it really empty?
> MainFrame::~MainFrame()
> {
> delete m_db; // this is where the crash happens
> }
When exactly is this destructor called?
Can you
Matthias-Christian Ott wrote:
> On 2016-01-25 16:47, Richard Hipp wrote:
>> On 1/25/16, Matthias-Christian Ott wrote:
>>>
>>> Does this mean that if I use SQLite SQLITE_EXTRA_DURABLE=0, PRAGMA
>>> journal_mode=DELETE and PRAGMA synchronous=FULL, SQLite could loose a
>>> transaction that it said
Hi, Teg,
On Mon, Jan 25, 2016 at 4:51 PM, Teg wrote:
> Hello Igor,
>
> Then I'd note the address of the object (make a copy of the pointer
> right as it's allocated) and then verify that the address you're
> deleting is the same as the address that was allocated. I've verify
> that
On Mon, Jan 25, 2016 at 5:08 PM, Richard Hipp wrote:
> On 1/25/16, Stephen Chrzanowski wrote:
> >
> > You also have to look at balance across many millions (or is it
> billions?)
> > of devices out there that use SQLite for their primary operations.
>
> Billions and billions.
>
Hello,
Anyone with any experiences with this (good or bad)?
Idea to have Sqlite database on server, accessed from a few ultra-thin
Terminal clients.
Best regards
Hello Igor,
Then I'd note the address of the object (make a copy of the pointer
right as it's allocated) and then verify that the address you're
deleting is the same as the address that was allocated. I've verify
that the correct calling convention is being used throughout too.
I'd
Hello J,
I don't typically use "new" in my C++ applications other than in
startup to allocate things that last the life of the application. So, I
don't have any issues with double-freeing. I never manually "new"
objects after startup. Instead I use containers to contains my objects
and leave the
Hi, Adam,
On Mon, Jan 25, 2016 at 2:46 PM, Adam Devita wrote:
> Hi Igor,
> I don't think you understood what I was trying to get at. Please
> allow me to rephrase: There isn't enough information about how things
> are being cleaned up to point out a problem, only make general
> suggestions
On 1/25/16, Howard Chu wrote:
>
> This is actually quite an unusual requirement; on older Unix systems you
> couldn't even *open* a directory, let alone obtain write access to it or
> fsync it.
Yeah. When the SQLITE_DISABLE_DIRSYNC compile-time option is present,
we disable the directory sync
On 25/01/16 14:14, Richard Hipp wrote:
> On 1/19/16, Meinlschmidt Stefan wrote:
>>
>> Shutting down power right after a successfully committed
>> transaction rolls back that transaction on next startup.
>
> Patches checked in:
>
> https://www.sqlite.org/src/info/30671345b1c1ee55
>
Hi Igor,
I don't think you understood what I was trying to get at. Please
allow me to rephrase: There isn't enough information about how things
are being cleaned up to point out a problem, only make general
suggestions about good practice.
This is why I was asking about where you would ensure
Hi, Adam,
On Mon, Jan 25, 2016 at 11:27 AM, Adam Devita wrote:
> Where do you pass to the dll something that goes to sqlite3_close(db); ?
> ( https://www.sqlite.org/c3ref/close.html )
> When that happens, does m_db get set to NULL (or now refers to memory
> that is now NULL)
> Do you check for
Hi, Peter,
On Mon, Jan 25, 2016 at 11:37 AM, Peter Aronson wrote:
> How are you building the DLL and the executable? Are they both including a
> copy of sqlite3.obj? Or are you using a sqlite3.dll?
I'm building SQLite from source.
The DLL and executable both do not reference
Hi, Teg,
On Mon, Jan 25, 2016 at 11:31 AM, Teg wrote:
> Hello Igor,
>
> MainFrame::~MainFrame()
> {
> delete m_db; // this is where the crash happens
> }
>
> I suspect you need to add a "Close" or destroy function to the DLL and
> pass the handle back to the DLL to let it get deleted in the
On Mon, Jan 25, 2016 at 12:22 PM, Simon Slavin wrote:
>
> On 25 Jan 2016, at 5:02pm, Bernard McNeill wrote:
>
> > Idea to have Sqlite database on server, accessed from a few ultra-thin
> > Terminal clients.
>
?I would guess that this harks back to the X terminal days. That is, a very
small
Hi,
I'm testing version 310.
and I'm quite sure that commit:
On unix, if a file is opened via a symlink, create, read and write
journal and wal files based on the name of the actual db file, not the
symlink.
introduce a bug in the following condition:
1. create a realive symlink
2. use
Hello Igor,
MainFrame::~MainFrame()
{
delete m_db; // this is where the crash happens
}
I suspect you need to add a "Close" or destroy function to the DLL and
pass the handle back to the DLL to let it get deleted in the DLL
context and not in the context of the caller.
extern "C"
Where do you pass to the dll something that goes to sqlite3_close(db); ?
( https://www.sqlite.org/c3ref/close.html )
When that happens, does m_db get set to NULL (or now refers to memory
that is now NULL)
Do you check for m_db == NULL before deleting it?
regards,
Adam DeVita
On Mon, Jan 25, 2016
Hi, Peter,
On Mon, Jan 25, 2016 at 10:50 AM, Peter Aronson wrote:
> Igor,
>
> You can't safely pass a SQLite handle between different SQL DLLs that way if
> they're both built with their own copy of the amalgamation (or link to
> things built with different copies). SQLite uses a handful of
On 1/25/16, Stephen Chrzanowski wrote:
>
> You also have to look at balance across many millions (or is it billions?)
> of devices out there that use SQLite for their primary operations.
Billions and billions.
> Slapping a serious performance decrease on devices where time and
> performance is
I have discovered that opening a database via a symlink works only if the
symlink is in the current directory. Otherwise, this happens:
; mkdir x y
; sqlite3 x/foo.sqlite 'create table foo(x);'
; sqlite3 x/foo.sqlite 'select count(*) from foo;'
0
; ln -s ../x/foo.sqlite y
; cmp x/foo.sqlite
On Mon, Jan 25, 2016 at 10:08 AM, Matthias-Christian Ott
wrote:
>
> If so, why isn't SQLITE_EXTRA_DURABLE=1 the default? Should correctness
> be more important than performance, except when the constraints are such
> that correctness has to be sacrificed for performance?
>
I wouldn't want that,
On 1/25/16, Matthias-Christian Ott wrote:
>
> Does this mean that if I use SQLite SQLITE_EXTRA_DURABLE=0, PRAGMA
> journal_mode=DELETE and PRAGMA synchronous=FULL, SQLite could loose a
> transaction that it said to be committed depending on the VFS?
Sort of. This appears to be true if you are
Hi Rowan!
>> Shutting down power right after a successfully committed
>> transaction rolls back that transaction on next startup.
>
> nitpick: This is sqlite behaving as advertised. See
> https://www.sqlite.org/lockingv3.html section 5.0 step 6, and
> https://www.sqlite.org/atomiccommit.html
Hi, Clemens,
On Mon, Jan 25, 2016 at 2:42 AM, Clemens Ladisch wrote:
> Igor Korot wrote:
>> Upon exiting from the application
>
> When exactly? Is DllMain() involved in any way?
The DLL where SQLite pointer is alocated there is a DLLMain.
Then this pointer is brought back to the main
On Mon, Jan 25, 2016 at 8:31 AM, Teg wrote:
> Hello Igor,
>
> extern "C" __declspec(dllexport) void DestroyObject(Database *db)
> {
> delete db;
> }
>
> It was my impression that each DLL got it's own heap so, memory
> allocated inside the DLL needs to be free'd inside the DLL. I use
>
How are you building the DLL and the executable? Are they both
including a copy of sqlite3.obj? Or are you using a sqlite3.dll?
Peter
On 1/25/2016 9:16 AM, Igor Korot wrote:
> Hi, Peter,
>
> On Mon, Jan 25, 2016 at 10:50 AM, Peter Aronson wrote:
>> Igor,
>>
>> You can't safely pass a SQLite
On 1/19/16, Meinlschmidt Stefan wrote:
>
> Shutting down power right after a successfully committed
> transaction rolls back that transaction on next startup.
Patches checked in:
https://www.sqlite.org/src/info/30671345b1c1ee55
https://www.sqlite.org/draft/compile.html#extra_durable
--
Igor,
You can't safely pass a SQLite handle between different SQL DLLs that
way if they're both built with their own copy of the amalgamation (or
link to things built with different copies). SQLite uses a handful of
global variables, but each DLL has its own copy of each of these global
Igor Korot wrote:
> Upon exiting from the application
When exactly? Is DllMain() involved in any way?
Regards,
Clemens
Adding the INDEXED BY changed the nesting order of the loops. Also, note the
word AUTOMATIC in the query plan: This means that the QP has decided it is
worthwhile to build an Index just for this one query.
The first plan in English:
Build an Index on T2.E = 2 that also contains the
On 1/19/16, Meinlschmidt Stefan wrote:
>
> Shutting down power right after a successfully committed
> transaction rolls back that transaction on next startup.
As you observe, this is a file-system dependent thing, and probably
only happens on the QNX filesystem. I will see if we can add a
I was analyzing hundreds of queries in our system and a few stood out
(average query time is subsecond, but these few that stood out were 10+
seconds).
Here is the basic query for these problem few:
SELECT T1.A from T1 INNER JOIN T2 on T1.B=T2.B and T1.C=T2.C where
T1.D='2015-12-31' and T2.E=2
If it matters, I'm trying Win 8.1 with MSVC 2010.
Thank you.
On Mon, Jan 25, 2016 at 12:18 AM, Igor Korot wrote:
> Hi, ALL,
> I have a strange problem.
>
> I am trying to use sqlite in my program. It has a main application and
> couplef DLLs.
>
> I am getting the connection in one of the DLL,
Hi, ALL,
I have a strange problem.
I am trying to use sqlite in my program. It has a main application and
couplef DLLs.
I am getting the connection in one of the DLL, then the pointer is passed up
to the main application.
Upon exiting from the application I'm trying to close the connection and
On Fri, Jan 22, 2016 at 1:29 PM, Richard Hipp http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users>>
wrote:
> That index will not work on queries like this (obviously):
>
>SELECT * FROM t1 WHERE x IS NULL;
>
>The index is also useless for sorting:
>
> SELECT * FROM t1
46 matches
Mail list logo
