Bug 16542 - Add Xamarin.iOS support for SqliteFunctions.
Summary: Add Xamarin.iOS support for SqliteFunctions.
Alias: None
Product: Class Libraries
Classification: Mono
Component: Mono.Data.Sqlite ()
Version: unspecified
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Untriaged
Assignee: Bugzilla
: 17081 ()
Depends on:
Reported: 2013-12-02 04:50 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2014-02-06 08:49 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Rolf Bjarne Kvinge [MSFT] 2013-12-02 04:50:13 UTC
Currently it is not possible to use SqliteFunctions in Xamarin.iOS, because the implementation depends on being able to create delegates to instance methods and then pass those delegates to native code:


This should be re-written to use static methods decorated with [MonoPInvokeCallback] attributes.

ref: https://bugzilla.novell.com/show_bug.cgi?id=679561
Comment 2 Rolf Bjarne Kvinge [MSFT] 2014-02-06 08:49:05 UTC

mono/master: 22cf2b620cea1b90acee9f4d42f1076739e2080d
monotouch/master: 0899ff79ac40e72fbc3a6a3379e223847f409ec7
Comment 3 Rolf Bjarne Kvinge [MSFT] 2014-02-06 08:49:27 UTC
*** Bug 17081 has been marked as a duplicate of this bug. ***