These columns have been provided for customer-specific purposes, and at the moment they are pain to update from external applications. This way MM5 inter-operability will be enhanced by removing the tokenizer issue for selected customx columns. or even better, add a checkbox for each of the customx columns, into Options|Library|Fieldsm to condition whether or not the column is to be covered by FTS. ![]() deliver some songs.customx fields that are not covered by FTS. My second preference would be as I requested during the alpha of MM5. That way we could do as Petr intended.Īre you planning this, or is it off the table? My first preference would be that you ship a 64 bit version of your sql-related dlls. It works, but it is not my first preference obviously. I would like to try it if he can make a 64 bit version.ĭeleting SQL insert triggers is not a good practice at all and I haven't tried using SQLite3MM.dll in my application, because I have a 64bit app atm. I didn't need to follow his other advice to get a convenient browser for MM database. Something which also fixed the tokenizer issue would be nice, but I have a workaround which is delete the SQL insert triggers for the Customx columns that I am updating. and load Petr's SQLite3MMExt.dll from 2014 open the MM5 db using the 32 bit version of this open source browser.I thought "the mentioned DB Browser for SQLite 3.12.1 32-bit" was referring to my discussion with Petr about an extension library for SQLITE browsers. ![]() I just tried the same with the mentioned DB Browser for SQLite 3.12.1 32-bit and I got: Entry Point Not Found - The procedure entry point sqlite3_create_function_v2 could not be located in the dynamic link library sqlite3.dll.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |