At 11:32 AM +0600 2/15/06, Kirill wrote:
Whether will be SqlLite in the future and under Mac OS if there will
be that as soon?
SQLite runs under Mac OS X right now, and has for a long time. A
version is even bundled with X.4 Tiger. -- Darren Duncan
Whether will be SqlLite in the future and under Mac OS if there will be that as
soon?
> -Original Message-
> From: Chris Schirlinger [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 14, 2006 8:45 PM
> To: sqlite-users@sqlite.org
> Subject: Re: Re[2]: [sqlite] To whom to inform on a bug?
>
> I tried the data you mentioned in SQLite Explorer and the SQL
> statemen
I tried the data you mentioned in SQLite Explorer and the SQL
statemen worked correctlyt:
> select * from tResult where tex like '%ra%'
returned the expected record perfectly
Here is the output of the command line test
SQLite version 3.3.3
Enter ".help" for instructions
sqlite> .schema
sorry :(
>> version:
>> 3.3.4 or 3.x
>>
>> System test:
>> Win2003(NTFS)
>>
>> Script:
>> select * from tResult where tex like '%ra%'
>> result = 0
>>
>> select tex from tResult where id = 3229
>> tex = "...Oracle..."
>>
>> Soft on broblem:
>> sqlite3explorer,
>> and my soft
Kirill <[EMAIL PROTECTED]> wrote:
> version:
> 3.3.4 or 3.x
>
> System test:
> Win2003(NTFS)
>
> Script:
> select * from tResult where tex like '%ra%'
> result = 0
>
> select tex from tResult where id = 3229
> tex = "...Oracle..."
>
> Soft on broblem:
> sqlite3explorer,
> and
version:
3.3.4 or 3.x
System test:
Win2003(NTFS)
Script:
select * from tResult where tex like '%ra%'
result = 0
select tex from tResult where id = 3229
tex = "...Oracle..."
Soft on broblem:
sqlite3explorer,
and my soft
sample db:
http://www.aidagw.com/files/dba.zip
dhc>
Kirill <[EMAIL PROTECTED]> wrote:
> hello
>
> select * from tResult where tex like '%ra%'
> result = 0
>
> select tex from tResult where id = 3229
> tex = "...Oracle..."
>
http://www.sqlite.org/cvstrac/tktnew
Hints: Unless you provide more information that you have
shown above, your ticket
hello
select * from tResult where tex like '%ra%'
result = 0
select tex from tResult where id = 3229
tex = "...Oracle..."
bag?
--
Kirill
"Robert Foster" <[EMAIL PROTECTED]> wrote:
> PHP Sessions are similar to session in ASP, ASP.Net, etc. Objects within
> the session are serialised into a stream and stored in the specified storage
> medium. By Default, PHP stores sessions in a file in the /tmp directory,
> identified by a unique
Comments below...
Robert Foster
General Manager
Mountain Visions P/L http://mountainvisions.com.au
-Original Message-
From: Jay Sprenkle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 15 February 2006 8:38 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] :memory: and sessions with
> You can also write custom session handlers, allowing you to store the
> session anywhere else including a database. There is some documentation on
> the Zend.com site for using the Session api, but it's simply a matter of
> writing some functions with specific names, and hooking them in via the
PHP Sessions are similar to session in ASP, ASP.Net, etc. Objects within
the session are serialised into a stream and stored in the specified storage
medium. By Default, PHP stores sessions in a file in the /tmp directory,
identified by a unique filename that is stored in a cookie on the browser
I light of Jay's comments about being unclear what Object Builder does,
I've added an additional page to cover that very concept at
http://www.ceamus.com/objbuilder/what.html
Anyone with more questions, feel free to hit me with them, on list or off.
And definitely feel free to use this code in
Hello,
I think the problem is that PHP uses a file-based
session serialization. Therefore anything that
cannot be saved to a file and returned ( eg. you
can't do this with file handles, etc. ) cannot be
saved in session scope in PHP as it is implemented
by default.
There is the 'mm' extension
On Wed, Feb 15, 2006 at 08:31:17AM +1300, CrazyChris wrote:
> We may be at crossed paths... I'm wanting to save the :memory: database to
> the session, not the other way round, so that when the 2nd page loads, the
> :memory: database can be recreated and available as it was on the last page
>
We may be at crossed paths... I'm wanting to save the :memory: database to
the session, not the other way round, so that when the 2nd page loads, the
:memory: database can be recreated and available as it was on the last page
load. The advantage is that after some time, the session is deleted
[EMAIL PROTECTED] wrote:
Is this right? You are doing a separate
CREATE TABLE for each message? That's going
to be the source of your problem. I think
Yes we are. I tried a message/row design
early on but I could not count on it being
behaving well. The problem was fitting
Outlook's
"Kervin L. Pierre" <[EMAIL PROTECTED]> wrote:
>
> How did you implement full text indexing?
> I though sqlite did not support full text
> index, am I wrong?
SQLite does not have *automatic* full-text indexing.
But it is easy enough to index the full text of an
email message yourself in
Hi,
Is it possible to use an :memory: database with a preallocated memory area ?
The locking mechanism could still use files, no problem. Or no locking (and I
provide the locking mechanism).
I have an application with a 5GB shared memory (with the SHM_HUGETLB flag -
Linux) and I do all de
[EMAIL PROTECTED] wrote:
I'm reading and replying to this message using an SQLite-backed
email client See
That's very interesting...
All incoming and archival emails are stored as BLOBs in a table.
The full text of messages is indexed. It is all very fast and
I haven't had to do anything
Andrew Piskorski <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 14, 2006 at 10:16:14AM -0500, Kervin L. Pierre wrote:
>
> > We are getting ready to start using in- memory database to cache
> > sqlite reads/writes in effort to improve speed. For background,
>
> > Since we read much more than we write,
> We are getting ready to start using in-
> memory database to cache sqlite reads/writes
> in effort to improve speed. For background,
> the application is an email client.
>
> The way we envision the caching working is
> that we have a mirror copy of any table in
> use in memory. The tables are
On Tue, Feb 14, 2006 at 10:16:14AM -0500, Kervin L. Pierre wrote:
> We are getting ready to start using in- memory database to cache
> sqlite reads/writes in effort to improve speed. For background,
> Since we read much more than we write, reading from memory should
> improve.
Shouldn't
Hello,
We are getting ready to start using in-
memory database to cache sqlite reads/writes
in effort to improve speed. For background,
the application is an email client.
The way we envision the caching working is
that we have a mirror copy of any table in
use in memory. The tables are small
> I think that I've previously mentioned my Object Builder code on this
> list. If I haven't, you might want to take a look at
> http://www.ceamus.com/objbuilder/
>
> Object Builder is a tool to automate the creation of Active Record classes
> for reading and writing data from databases. The
I think that I've previously mentioned my Object Builder code on this
list. If I haven't, you might want to take a look at
http://www.ceamus.com/objbuilder/
Object Builder is a tool to automate the creation of Active Record classes
for reading and writing data from databases. The included
27 matches
Mail list logo
