HTTP started with the idea that it would be possible to connect via
HTTP, for tunneling purposes.
I have been looking at the links and suggestions and have reached the
following conclusions:-
1) Adding general purpose web server capabilities in uSQL would be a
mistake. The purpose is to add
uSQLite does not (generally) enter into the details of the query it is
passed. There is however an exception for security. uSQLite requires a
login and (depending on the user and network) assigns the user a level:
0: No access
1: Select only
2: Update/Insert only
3: Select/Update/Insert only
4:
[EMAIL PROTECTED] wrote:
uSQLite does not (generally) enter into the details of the query it is
passed. There is however an exception for security. uSQLite requires a
login and (depending on the user and network) assigns the user a level:
0: No access
1: Select only
2: Update/Insert only
3:
> Original Message
> Subject: Re: [sqlite] SQL syntax possibilities
> From: Eric Bohlman <[EMAIL PROTECTED]>
> Date: Wed, November 16, 2005 10:54 am
> To: sqlite-users@sqlite.org
>
> [EMAIL PROTECTED] wrote:
> > uSQLite does not (generally) enter into the details of the query
Nathan Kurz wrote:
> I'm using a computationally expensive user defined function called
> 'match()'. In case it makes a difference, match() is written in C,
> and for testing, I'm loading it as a shared library into the sqlite3
> shell application. I want to return the value of match(), and also
* D. Richard Hipp:
> If an error occurs in a step function, record that fact in
> the aggregate context. Then when the finalizer is called,
> check the error flag in the context and call sqlite3_result_error
> at that point if it is appropriate to do so.
Does this really work? According to my
I have a little engine doing HL7 messaging using SQLite3 from Tcl
(Windows Server 2003 with a local attached RAID 5 for database).
I'm looking for some speed improvements, so yesterday I experimented
with PRAGMA synchronous = OFF. Holy Cats - it's WAAAY faster - like
night and day.
So, I'd like
I'd be interested in seeing that code--there's always something to be
learned from another implementation.
For those interested, I've put my code up at:
http://www.poweradmin.com/sourcecode/index.asp (HTTPServer.zip--you'll
see it)
I welcome any feedback. Probably better to send it to my
At 15:52 16/11/2005, you wrote:
I'd be interested in seeing that code--there's always something to be
learned from another implementation.
For those interested, I've put my code up at:
http://www.poweradmin.com/sourcecode/index.asp (HTTPServer.zip--you'll
see it)
I welcome any feedback.
* Nathan Kurz:
> On Wed, Nov 16, 2005 at 01:16:40PM +0100, Florian Weimer wrote:
>> * D. Richard Hipp:
>>
>> > If an error occurs in a step function, record that fact in
>> > the aggregate context. Then when the finalizer is called,
>> > check the error flag in the context and call
At 1:34 AM -0700 11/16/05, [EMAIL PROTECTED] wrote:
uSQLite does not (generally) enter into the details of the query it is
passed. There is however an exception for security. uSQLite requires a
login and (depending on the user and network) assigns the user a level:
0: No access
1: Select only
> Original Message
> Subject: Re: [sqlite] SQL syntax possibilities
> From: Darren Duncan <[EMAIL PROTECTED]>
> Date: Wed, November 16, 2005 10:41 pm
> To: sqlite-users@sqlite.org
>
> At 1:34 AM -0700 11/16/05, [EMAIL PROTECTED] wrote:
> >uSQLite does not (generally) enter
Is the source available for this nano web server?
--- [EMAIL PROTECTED] wrote:
> FWIW, the www.sqlite.org website is implemented using a
> webserver written as a single file of C code - 752 lines
> (exclusive of comments). It's unix-specific though, and
> in fact really wants to run on Linux.
>
Joe Wilson <[EMAIL PROTECTED]> wrote:
> Is the source available for this nano web server?
>
> --- [EMAIL PROTECTED] wrote:
> > FWIW, the www.sqlite.org website is implemented using a
> > webserver written as a single file of C code - 752 lines
> > (exclusive of comments). It's unix-specific
If the power never goes out and no programs ever crash on you system then
Synchronous = OFF is for you, but the rest of the world might still want it
ON. Really it sounds like the thing you need to worry about most is the
unexpected termination of your program. If you aren't worried about
"Preston Z" <[EMAIL PROTECTED]> wrote:
> If the power never goes out and no programs ever crash on you system then
> Synchronous = OFF is for you, but the rest of the world might still want it
> ON.
Minor clarification: Program crashes will not cause data corruption with
synchronous=off. But
Roger,
I am on the road at the moment, but will be home in a week and can give you the
essence of a very simple HTTP server and client, with socket interface for Unix
and Win32. In an embedded world you only need it simple.
JS
Quoting [EMAIL PROTECTED]:
>
>
> >
> > HTTP is just a
17 matches
Mail list logo
