Simon Slavin-3 wrote
> https://www.sqlite.org/src/artifact?ci=trunkfilename=ext/icu/README.txt;
However the example described here is a little bit simplistic:
lower('I', 'en_us') -> 'i'
lower('I', 'tr_tr') -> 'ı' (small dotless i)
You depend on the encoding of the text editor,
Simon Slavin-3 wrote
> Unfortunately, bare SQLite understands only ASCII characters. It does not
> understand Unicode. To build in full understanding of Unicode would make
> SQLite almost twice as long.
>
> However, you can add Unicode support to SQLite using ICU:
>
>
Simon Slavin-3 wrote
> See section 1.1 of
>
> https://www.sqlite.org/src/artifact?ci=trunkfilename=ext/icu/README.txt;
>
> Simon.
It looks good, basically 2 letter ISO 639 language code and ISO 3166 country
code.
--
Sent from: http://sqlite.1065341.n5.nabble.com/
The example you found is not applicable in your case, because it is
describing an way to develop your own functions in PHP, which is not the
case for you.
--
Sent from: http://sqlite.1065341.n5.nabble.com/
___
sqlite-users mailing list
According to SQLite documentation, it does not depend on locale, because it
is a pure ASCII implementation:
"The upper(X) function returns a copy of input string X in which all
lower-case ASCII characters are converted to their upper-case equivalent."
ASCII character was designed for English US,
Dr. Mucibirahman İLBUĞA wrote
> And I really shocked that am I first person on over the world who wants to
> use SQLite in their own language?... :)
You are not the first person that uses SQLite with a different character set
than ASCII and with a different locale other than English US. If you
tion, but I noticed no message, so for me it looks like
the WAL feature was not enabled. By analyzing the existed traces it looks
like thread 2 - reader is getting a SHARED lock, while later process 3 -
writer is trying to get an EXCLUSIVE lock.
Any suggestion would b
(EXCLUSIVE,1) pid=233565 tid=20 (unix)
LOCK13 SHARED failed (unix)
UNLOCK 13 0 was 0(4,1) pid=233565 tid=20 (unix)
ROLLBACK 139547936
Regards,
Sandu Buraga
Date: Thu, 31 Oct 2013 14:05:17 -0400
From: Richard Hipp <d...@sqlite.org>
To: General Discussion of SQLite Database <sql
?
Regards,
Sandu
On Mon, Nov 11, 2013 at 6:33 PM, Sandu Buraga <sandu.bur...@gmail.com>wrote:
> Hi,
>
> I took your advice and now I am setting only once the journal_mode=WAL,
> also locking_mode=EXCLUSIVE and temp_store=MEMORY. But still it doesn't
> work, and I get DB locks i
( m_FilePath.getBuffer(), ,
SQLITE_OPEN_READWRITE|SQLITE_OPEN_FULLMUTEX|SQLITE_OPEN_PRIVATECACHE, NULL
);
Regards,
Sandu Buraga
>> On Mon, Nov 11, 2013 at 12:33 PM, Sandu Buraga <sandu.bur...@gmail.com>wrote:
>>
>>> Hi,
>>>
>>> I took your advice and no
to believe that WAL is not a viable choice on a QNX system.
Regards,
Sandu
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
EXCLUSIVE lock is never released. The
next locks requests will fail.
Regards,
Sandu Buraga
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
0(4,1) pid=229454 tid=20 (unix)
ROLLBACK 139532984
So, the same process, it is clear that no other process/thread is accessing
the database. Why the EXCLUSIVE lock acquired during the WAL enabling is
not released?
Regards,
Sandu Buraga
___
sqlite-users m
course the
database file will be locked, and cannot be used by other process.
Maybe the WAL documentation should be extended with a note for QNX.
Regards,
Sandu
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ocked" errors, either in the write or read thread.
Since the new content is not committed yet, why I am getting this errors?
My expectations would've been that during the end transaction to have such
errors, but not long before.
Regards,
Sandu
___
sq
out was set only for one of the connections.
But, anyway the table lock continued to be triggered immediately not
waiting to pass 2500 ms.
I thought that WAL should've solved this aspect about the concurrency, but
it seems that for DELETE statements it still needs
will be visible for all the handles?
Regards
Sandu
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
with one writer and 2 readers, and
I am getting 'database table is locked' errors. The write statements:
INSERT, INSERT OR UPDATE, DELETE are encapsulated in a transaction and I am
using WAL mode.
Regards
Sandu
___
sqlite-users mailing list
sqlite-users
simultaneously, using WAL.
Thanks
Sandu
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
In Arabic you have a different direction of the text. Might be that the
reason?
Sandu
Eric Minbiole schrieb am Di., 11. Sep. 2018, 00:23:
> > SELECT rowid,text
> > FROM table
> > WHERE table MATCH 'أعلم*';
> >
> > And I have to add this that my data is Arabic
20 matches
Mail list logo