On 25/05/2009 2:30 PM, Philip Warner wrote:
> I use binary GUID values and when I 'select' them in the sqlite3 shell,
> they display as *binary* data, often screwing up the terminal. When I
> use .dump, or use .mode tcl I get terminal-friendly output. Is there any
> simple way (or just a hack)
Hi,
I'm using sqlite3 and am very impressed. But, have one small problem.
I use binary GUID values and when I 'select' them in the sqlite3 shell,
they display as *binary* data, often screwing up the terminal. When I
use .dump, or use .mode tcl I get terminal-friendly output. Is there any
simple
"Sam Carleton"
wrote in message
news:8d38ca0a0905241955j2f5f8062l43e68c8f9e48f...@mail.gmail.com
> I am using julianday('now') to set the insertedon date to my tables.
> The value needs to be returned to the client via Web Service so that
> the client and return it
Hi Dan,
I checked the implementation of back up API and did not notice anywhere
had turned on "PRAGMA locking_mode=exclusive" or any other similar PRAGMA
explicitly.
And another thing wonder me is why I did not see the journey file before
power off ?
>
> > b. There always a journey file
I am using julianday('now') to set the insertedon date to my tables.
The value needs to be returned to the client via Web Service so that
the client and return it later to get the next inserted record. I am
currently returning it as a double, somewhere along the way it is
getting trunkated:
From
On 24/05/2009 4:30 AM, Lukas Haase wrote:
> Hi,
>
> Sorry for the subject - I just do not know for what to search of what to
> ask - I actually do not know where is exactly my problem :-(
>
> I have a database containing thousands of HTML pages ("topics"). There
> is a fulltext index for these
On 24 May 2009, at 1:28pm, Lukas Haase wrote:
> Simon Slavin schrieb:
>> On 23 May 2009, at 7:30pm, Lukas Haase wrote:
>>> SELECT topic_fulltext.topicID
>>> FROM fulltext
>>> JOIN topic_fulltext ON topic_fulltext.fulltextID =
>>> fulltext.fulltextID
>>> WHERE word LIKE 'Word%';
>>
>> WHERE
On Sun, May 24, 2009 at 02:28:36PM +0200, Lukas Haase wrote:
>
> SELECT topic_fulltext.topicID
> FROM fulltext
> JOIN topic_fulltext ON topic_fulltext.fulltextID = fulltext.fulltextID
> WHERE (word LIKE 'Word1%') AND (word LIKE 'Word2%');
Obviously this must be empty because a string can't start
"Lukas Haase" wrote in
message news:gv9fcm$5r...@ger.gmane.org
> I have a database containing thousands of HTML pages ("topics"). There
> is a fulltext index for these topics. First there is a table
> containing all single words. Each word is identified by its
> "fulltextID":
>
Hi,
Igor Tandetnik schrieb:
> "Lukas Haase" wrote in
> message news:gv9fcm$5r...@ger.gmane.org
>> I have a database containing thousands of HTML pages ("topics"). There
>> is a fulltext index for these topics. First there is a table
>> containing all single words. Each word is
Hi,
At first, thank you for your answer!
Simon Slavin schrieb:
> On 23 May 2009, at 7:30pm, Lukas Haase wrote:
>> SELECT topic_fulltext.topicID
>> FROM fulltext
>> JOIN topic_fulltext ON topic_fulltext.fulltextID = fulltext.fulltextID
>> WHERE word LIKE 'Word%';
>>
>> But now I want to be able
11 matches
Mail list logo