Each major release (and occasionally minor) we review third party libraries and
what improvements have been released since we last looked.
FTS and having international support for a fast search within our app has been
a big push. We are essentially a glorified database front end with a cushy
On 16 Jun 2014, at 3:38am, Josh Wilson wrote:
> It would appear I kept copying an old file for v3.8.4.3 and not the actual
> v3.8.5 I was modifying so no wonder there was no change. So after a `Clean`
> and `Delete Derived Data` then build the resulting build worked.
You could create a fake framework, because it takes a while every time to
compile.
Just wondering: What's your rationale to use Unicode61 in an iOS project? Being
able to sort based on the locale is a feature all our foreign customers demand
(and here in German as well). Of course nobody will
Righteo thanks for the sanity check that it must be me at fault and that this
is indeed possible without ICU.
I have a separate XCode project for rolling the latest SQLite amalgamation
and copy that built library out of the Derived Data folder into our main App
project.
It would appear I kept
On Sun, Jun 15, 2014 at 10:02 PM, Josh Wilson
wrote:
> https://bitbucket.org/ottersoftware/fts-diacritic-marks
>
> Ok so the above project successfully includes a build of sqlite v3.7.15.2
> without ICU but the `unicode61` tokenizer works.
>
> So I tried the same
https://bitbucket.org/ottersoftware/fts-diacritic-marks
Ok so the above project successfully includes a build of sqlite v3.7.15.2
without ICU but the `unicode61` tokenizer works.
So I tried the same #defines they used with v3.8.5 and still get 'unknown
tokenizer: unicode61'
Has something
Thanks Ben.
Ok that makes sense. Normally if you roll the source code yourself there are
no issues since you are taking responsibility for the code being delivered
to the AppStore.
I know that sometimes Apple insta-rejects based upon the symbols in your
binary. Collisions with private APIs makes
I use SQLite with some custom extensions + ICU (+ some small additions to
enable loading minimized ICU dat files) since almost 3 years in all our
companies' iOS projects. I came across a posting once on StackOverflow
with somebody saying he got a rejection - but this was never the case for
us and
This might seem like a dumb question but I am getting conflicting
information from web sources.
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1218086.html
I'm trying to enable unicode61 tokenizer for a build on iOS. Apple frowns
upon including your own libicu since they
> On 15 Jun 2014, at 5:21pm, Eric Rubin-Smith wrote:
>
> still not good enough for my use case
> (unfortunately). Any further optimization tips are highly welcome.
Strongly suspect that although R*Trees produce an elegant solution to your
problem, the fact that they're a
On Sun, Jun 15, 2014 at 9:47 AM, Eric Rubin-Smith wrote:
> Richard Hipp wrote:
>
> > What does this query return?
> >
> > SELECT count(*) FROM ipIndex
> > WHERE minD1 <= 1220818432 and 1220818432 <= maxD1
> > AND minD2 <= 2120561472 and 2120561472 <= maxD2
>
Richard Hipp wrote:
> What does this query return?
>
> SELECT count(*) FROM ipIndex
> WHERE minD1 <= 1220818432 and 1220818432 <= maxD1
> AND minD2 <= 2120561472 and 2120561472 <= maxD2
> AND minD3 <= 1685398080 and 1685398080 <= maxD3
> AND minD4 <= 1685755328
Hello,
I've taken the time to investigate the problem: only the last
parameter is not correctly bound to NULL.
May I suggest a patch:
--- shell_.c 2014-06-15 14:22:39.0 +0200
+++ shell.c 2014-06-15 14:23:11.0 +0200
@@ -2553,7 +2553,7 @@
"filling the
On Sun, Jun 15, 2014 at 12:25 AM, Eric Rubin-Smith
wrote:
>
> sqlite> explain query plan SELECT prefix, target FROM routeTarget WHERE id
> = (
>...>SELECT id FROM ipIndex
>...> WHERE minD1 <= 1220818432 and 1220818432 <= maxD1
>...> AND minD2 <=
14 matches
Mail list logo