[Mono-dev] System.Data.SQLite changes that may interest Mono users

[znarF]

Disregard my previous post - I misread the sqlite version.

Now using Sqlite 3.6.3, and getting less errors.  Seems to be an issue with
the fill command, and the sqlite3_column_origin_name symbol is missing.

Mmm, maybe you weren't kidding when you said 3.6.1 is the only working one
at this point...

I'll give it a shot.



znarF wrote:
> 
> Hi Robert,
> I'm trying to use the managed libraries of the updated version of
> System.Data.Sqlite in FreeBSD with mono.
> 
> I've updated my ports tree - using SQLite version 3.5.6.  When running my
> sqlite tests, I get the following exception when trying to access the
> database:
> System.Data.SQLite.UnsafeNativeMethods:sqlite3_next_stmt at
> System.Data.SQLite.SQLiteBase.ResetConnection at
> ...CloseConnection at
> ...ReleaseHandle at
> ...Dispose at
> ...Sqlite3.Close at
> ...SqliteConnection.Close at
> ...SqliteConnection.Open
> 
> Doing an nm on the shared object library shows that this symbol
> (sqlite3_next_stmt) is missing.
> 
> Is the updated version only workable with SQLite 3.6.1?
> Thanks
> 
> 
> Robert Simpson wrote:
>> 
>> I just posted version 1.0.55.0 of the System.Data.SQLite provider here:
>> 
>> http://sqlite.phxsoftware.com
>> 
>>  
>> 
>> Included in this update is an option to recompile the managed provider
>> portion of the code with a SQLITE_STANDARD preprocessor symbol defined. 
>> If
>> set, the provider will compile as managed only and p/invoke against the
>> stock "sqlite3" library with about 99% functionality of my modified
>> version.
>> 
>>  
>> 
>> I also added the URI connection string from Marek's mono modifications. 
>> I
>> *think* that at this point all you'd have to do is rename the namespace
>> and
>> re-case the class names to get my provider sync'd up to the
>> Mono.Data.Sqlite
>> provider.
>> 
>>  
>> 
>> If anyone's interested in working on that and giving me feedback, I'd be
>> happy to make any other changes needed in my version to help keep the
>> mono
>> edition as easy to maintain for you guys as possible.
>> 
>>  
>> 
>> One major caveat:  Dr. Hipp only just this version (3.6.1) added
>> precompiled
>> binary support for several metadata API functions.  The Mono.Data.Sqlite
>> provider was p/invoking these functions already, but the default binary
>> from
>> sqlite.org did not export them.  They included
>> sqlite3_table_column_metadata(), sqlite3_column_orig(), and several other
>> metadata-related functions.
>> 
>>  
>> 
>> As such, the only version of System.Data.SQLite (and in fact any version
>> of
>> the Mono.Data.Sqlite provider) that will pass a complete round of unit
>> tests
>> is when backed to SQLite 3.6.1.
>> 
>>  
>> 
>> Robert
>> 
>>  
>> 
>> 
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>> 
>> 
> 
> 

-- 
View this message in context: http://n2.nabble.com/System.Data.SQLite-changes-that-may-interest-Mono-users-tp677121p1131210.html
Sent from the Mono - Dev mailing list archive at Nabble.com.