Skip to content

Unimplemented API list #15

@bordoley

Description

@bordoley

= API with patches =
sqlite3_limit - If supported would be on SQLiteDatabaseConnection ericsink/SQLitePCL.raw#36

= Need to write patches for =
sqlite3_busy_handler - #9
sqlite3_extended_result_codes - Supported in Raw. Should probably always enable this to simplify the creation code in SQLiteException.

= Future =
sqlite3_threadsafe - Should be added as a method on SQLite3
sqlite3_config - Should be added as a method on SQLite3
sqlite3_collation_needed - I can't really see a use in ever implementing this except for error handling perhaps. If supported would be on SQLiteDatabaseConnection
sqlite3_create_module - If supported would be on SQLiteDatabaseConnection
sqlite3_create_module_v2 - If supported would be on SQLiteDatabaseConnection
sqlite3_db_config - If supported would be on SQLiteDatabaseConnection
sqlite3_db_release_memory - If supported would be on SQLiteDatabaseConnection
sqlite3_overload_function - If supported would be on SQLiteDatabaseConnection
sqlite3_release_memory - SQLite3 static method if added
sqlite3_stricmp / sqlite3_strnicmp - SQLite3 static method if added
sqlite3_strglob - SQLite3 static method if added
sqlite3_mprintf / sqlite3_snprintf / sqlite3_vsnprintf / sqlite3_vmprintf - SQLite3 static method if added
sqlite3_unlock_notify - If supported would be on SQLiteDatabaseConnection
sqlite3_soft_heap_limit64 - SQLite3 static method if added
sqlite3_vfs_find / sqlite3_vfs_register / sqlite3_vfs_unregister - VFS APIs not supported yet in raw. This is very future.
sqlite3_wal_hook - If supported would be on SQLiteDatabaseConnection

= Not Needed =
sqlite3_errcode - Supported in Raw. Doesn't seem needed in pretty.
sqlite3_bind_blob64/sqlite3_result_blob64 - Not needed without large array support (see: http://msdn.microsoft.com/en-us/library/hh285054(v=vs.110).aspx)
sqlite3_bind_value - Not needed
sqlite3_column_value - Not needed
sqlite3_get_table - This is a legacy interface
sqlite3_get_auxdata / sqlite3_set_auxdata- Not needed. C# scalar funcs can use closure over external data like the compiled regex in the example, so doesn't seemed needed.
sqlite3_sleep - why?
sqlite3_context_db_handle - Would require passing a IDatabaseConnection or SQLiteDatabaseConnection to the callback functions for aggregate/scalar. Better to let those function use closure.
sqlite3_randomness - Use the .net random number generator
sqlite3_initialize/sqlite3_shutdown - aid in process initialization and shutdown on embedded systems. Workstation applications using SQLite normally do not need to invoke either of these routines.
sqlite3_os_init/sqlite3_os_end - The application should never invoke either sqlite3_os_init() or sqlite3_os_end() directly.
sqlite3_msize - SQLite memory management
sqlite3_auto_extension / sqlite3_cancel_auto_extension / sqlite3_reset_auto_extension- Used for loading statically linked extensions. Inheritently not xplat.
sqlite3_log - Managed code can use managed logging?
sqlite3_uri_boolean / sqlite3_uri_int64 / sqlite3_uri_parameter - used by vfs implementations
sqlite3_vtab_config / sqlite3_vtab_on_conflict / sqlite3_declare_vtab - used virtual table implementations.
sqlite3_file_control - used by vfs implementations
sqlite3_value_numeric_type - would require exposing a concrete SQLiteValue implementation.
sqlite3_value_bytes16 - UTF16 API

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions