Subject: Re: [sqlite] Question on missing Entry Point for Sqlite 3
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> W Allan Edwards wrote:
> > By preprocessor do you mean #define?
>
> It is a #define if in C source and -D if a compiler argument.
>
platform. : - )
You guys are awesome at support. Thanks again for exploration of this issue
with me.
Allan> Date: Mon, 9 Feb 2009 14:17:30 -0800> From: rog...@rogerbinns.com> To:
sqlite-users@sqlite.org> Subject: Re: [sqlite] Question on missing Entry Point
for Sqlite 3> &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Richard Hipp wrote:
> These two factors are sufficient to convince me to leave it turned off
> by default.
You are aware that last year you turned it on by default for the
libraries you build :-)
http://www.sqlite.org/cvstrac/chngview?cn=5539
On Feb 9, 2009, at 10:19 AM, W Allan Edwards wrote:
>
> you would think for desktop Linux (Ubuntu) with the average pc
> carrying 2 gigs of ram today they would compile t with all
> configurations on.
There are a couple of factors here.
(1) I am philosophically opposed to the entire
SQLI
all features if it is over say... 4 megabytes? hehe Almost seems now
> you need a sqliter.. but 300 million installs later can't be wrong.
>
> Allan
>
>
>> Date: Mon, 9 Feb 2009 08:53:12 -0600
>> From: jo...@viacognis.com
>> To: sqlite-users@sqlite.org
>&g
On Mon, Feb 9, 2009 at 3:19 PM, W Allan Edwards
wrote:
> I thought sqlite was originally designed and developed by Dr. Hipp so he
> could learn database technology? (SQL database stuff) Then after years and
> years and 3 versions later the thing has found it's way into all kinds of
> devices d
..@viacognis.com
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Question on missing Entry Point for Sqlite 3
>
> You do not appear to understand the intent of Sqlite. It is an open
> source software library which can be comiled to siuit unique application
> requirements.
plodes and I get that import message.
>
> FYI
>
> http://sqlite.phxsoftware.com/
>
> From: silicon_pla...@hotmail.com
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] Question on missing Entry Point for Sqlite 3
> Date: Sun, 8 Feb 2009 22:47:33 -0600
>
>
>
&
@sqlite.org
Subject: RE: [sqlite] Question on missing Entry Point for Sqlite 3
Date: Sun, 8 Feb 2009 22:47:33 -0600
> That doesn't make any sense. (you sound like all my old girlfriends) Did you
> mean sqlite3.c? If you define the
> same thing multiple times in the same compil
lt;<<<<<<<<<<<<<<<<<<<<<<<
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W Allan Edwards wrote:
> By preprocessor do you mean #define?
It is a #define if in C source and -D if a compiler argument.
> I did a search in my sqlite.c file for
>
> SQLITE_ENABLE_COLUMN_METADATA.. then I #defined above them ALL!
That doesn't
On 9/02/2009 2:47 PM, W Allan Edwards wrote:
>
> By preprocessor do you mean #define? I did a search in my sqlite.c file for
>
> SQLITE_ENABLE_COLUMN_METADATA.. then I #defined above them ALL!
The usual way of doing such a thing is somewhat less intrusive and
labour-intensive and easier to ge
would have something do with the .configure fun
file?
> Date: Sun, 8 Feb 2009 18:10:19 -0800
> From: rog...@rogerbinns.com
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Question on missing Entry Point for Sqlite 3
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W Allan Edwards wrote:
> You then tell me to go define that symbol in my c source file
No. You have to have it defined when compiling SQLite. Defining it
elsewhere such as your C source will have no effect. It affects the
compilation of SQLite
pecifically C/C++) will
help you with tech realization at all levels! : - ) But you adding that in is
VERY helpful, it cuts the ambiguity in your communication.
Allan
> Date: Sun, 8 Feb 2009 14:34:17 -0800
> From: rog...@rogerbinns.com
> To: sqlite-users@sqlite.org
> Subject: Re: [sq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W Allan Edwards wrote:
> I find it odd you have different expected behavior for the same code on each
> different platform.
What specifically are you referring to there?
> The windows version works great... when I move the "same" code over to
the mo
ntry point offerings for each platform
of the same sqlite database version?
Allan
> Date: Sun, 8 Feb 2009 13:24:32 -0800
> From: rog...@rogerbinns.com
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Question on missing Entry Point for Sqlite 3
>
> -BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W Allan Edwards wrote:
> What is interesting is that on windows the same managed provider works fine
> (sqlite). But on linux I receive this error.
That is because the Windows SQLite DLL is compiled by the SQLite team
with SQLITE_ENABLE_COLUMN_METAD
using the same versions of the same
tools?
Allan
> Date: Wed, 4 Feb 2009 01:03:48 -0800
> From: rog...@rogerbinns.com
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Question on missing Entry Point for Sqlite 3
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W Allan Edwards wrote:
> Unhandled Exception: System.EntryPointNotFoundException:
> sqlite3_column_origin_name
Consult the documentation:
http://www.sqlite.org/c3ref/column_database_name.html
Note that SQLITE_ENABLE_COLUMN_METADATA must be defined w
Unhandled Exception: System.EntryPointNotFoundException:
sqlite3_column_origin_name
I am getting this issue on a mono based application that utilizes the sphinx
.net 2.0 ado.net adaptor for sqlite. I have installed the latest sqlite on my
Ubuntu Linux 8.10 but I get this issue. My guess is m
21 matches
Mail list logo
