There is no \ at the end of the code which was pasted.
did you removed them from the source ?
the error look related to that problem.
my .02 $
2017-02-14 17:20 GMT-05:00 Simon Slavin :
>
> On 14 Feb 2017, at 10:15pm, Bart Smissaert
> wrote:
>
> > The strange thing is that nil changed other th
looks like a race condition!
but it could also be uninitialized variable, but this is rarer these day as
most compiler flag uninitialized var.
unless your uninitialized var happen to be in a struct, this is why
constructor are so important for struct/class
2017-02-27 11:28 GMT-05:00 Jeff Arc
Hi Roshak,
Looks like your top function in that thread is sqlite3_prepare_v2
So I can assume 2 things:
1 - you started a thread directly on sqlite3_prepare_v2
2- you erase part of the stack trace.
if you did 1, I can only say this is not good!
if you did 2, then you are keeping information, wh
Sybase has one.
there is even a way to get objects dependencies, I have been working on a
project for the last 5 years using sybase (ASE). very huge project and
whenever we must alter the schema we have tools to tell us which store
proc, triggers, views will be impacted. it allow us to reach the d
Yep Sybase preparse it. When you create a view/sproc/triggers/function the
objects referenced must exist or your DDL will fail.
this create some complexity when we want to recreate all the objects, order
of creation is very important.
2017-03-23 21:15 GMT-04:00 Simon Slavin :
>
> On 24 Mar 201
I see no problems with C++.
Mem is only foward declared, you can redefined it to whatever you want. as
long as you do not redefined it for sqlite.c you should be good.
in sqlite.h it's declared:
struct Mem;
so in your code if you do:
struct Mem { int a;int b;} then your definition will be used
Ah, understood.
I thought you had a struct or a class named Mem.
then short term solution is to rename Mem in sqlite.h
using the #define directive + include file should do the trick.
as they say solve it by using a level of indirection!
It will be a bit ugly, but until
a) sqlite change the na
as Sqlite is already within extern "C"
I'm wondering how your namespace trick can work ?
2017-04-10 9:41 GMT-04:00 Bob Friesenhahn :
> On Mon, 10 Apr 2017, Olivier Mascia wrote:
>
>>
>> This is where I do:
>>
>> #include "memory.h"
>> namespace sqlite
>> {
>> #include "sqlite3.h"
>> }
>>
>> An
namespace
2017-04-10 10:43 GMT-04:00 Olivier Mascia :
> > Le 10 avr. 2017 à 16:21, Daniel Anderson a écrit :
> >
> > as Sqlite is already within extern "C"
> >
> > I'm wondering how your namespace trick can work ?
>
>
> Both are si
you would probably be better off using C++ to handle everything, less
chances of forgetting to close something.
do not build your own classes, use existing one!
2017-04-14 10:44 GMT-04:00 Igor Korot :
> Keith,
>
> On Fri, Apr 14, 2017 at 10:37 AM, Keith Medcalf
> wrote:
> >
> > To further clari
ite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org]
> > On Behalf Of Daniel Anderson
> > Sent: Friday, 14 April, 2017 21:11
> > To: SQLite mailing list
> > Subject: Re: [sqlite] Create database
> >
> > you would probably be better off using C++ to handle everything,
the article was integers (4 bytes) vs guid as a primary key, which as
string takes 36 bytes. so he was right in saying that string guid/uuid take
9 time the space of simple integers.
in general the article was quite good and allowed people to ponder about
their choices/beliefs.
he said be: *caref
I drink to that!
2017-06-10 14:26 GMT-04:00 Jens Alfke :
>
> > On Jun 10, 2017, at 6:58 AM, Daniel Anderson wrote:
> >
> > the article was integers (4 bytes) vs guid as a primary key, which as
> > string takes 36 bytes. so he was right in saying that string guid/uuid
13 matches
Mail list logo