Will SQLite at least always be an option? Because I need SQLCipher for the encryption. Unless ForestDB will have encryption? Forgive me if it already does. Also FTS would definitely be useful. I think I read somewhere that ForestDB's implementation doesn't have all the capabilities of SQLite's FTS4? But perhaps it's good enough for what I need, which is basic AND, OR, and prefixed searches (e.g. Term* to return "Terminator"). Although being able to search for substrings would be a huge bonus, especially for Chinese, Japanese, Korean, etc. type languages.
Thanks! Brendan On Wednesday, June 17, 2015 at 4:40:56 PM UTC-7, Jens Alfke wrote: > > > On Jun 17, 2015, at 4:29 PM, Brendan Duddridge <bren...@gmail.com > <javascript:>> wrote: > > Perhaps one alternative might be for me to prefix the value with the field > identifier and then whenever I query, I could include the value they enter > prefixed with the field identifier? So something like: > > > That’s a possibility, as long as you put a prefix or something on the > field identifier to make it not match any real word. > > Although that also depends on how SQLite is compiled. I compile my own > because I use SQLCipher. > > > Yeah, and in general don’t rely on anything about SQLite, because in the > future we’ll have a different storage engine. > > —Jens > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to mobile-couchbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/f277d051-8982-4610-99db-24ef2b30bf92%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
