"Roger Binns" <[EMAIL PROTECTED]> wrote:
> > The new SCM I (and others) are working on will allow you to
> > quickly and easily download the entire source code/wiki/ticket
> > repository and/or synchronize your local repository with remote
> > changes. So ultimately this will not be an issue.
D.Richard Hipp <[EMAIL PROTECTED]> wrote:
>Perhaps it would be sufficient to take snapshots of the wiki and
>ship that with each release?
Yes, shipping wiki snapshots with each build should be fine.
Even better: A versioned wiki - so users of legacy versions can edit and
improve documentation
The new SCM I (and others) are working on will allow you to
quickly and easily download the entire source code/wiki/ticket
repository and/or synchronize your local repository with remote
changes. So ultimately this will not be an issue. But all that
is still in the future.
Is this available
Ralf Junker <[EMAIL PROTECTED]> wrote:
>
> This is especially valuable for all all who need to work with older versions
> of the SQLite because their environment has not yet updated to the latest
> release. It can be very unfortunate for them to find updated information
> which might be
[EMAIL PROTECTED] wrote:
Eric Bohlman <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > I'm thinking that all documentation is better placed in
> > a wiki.
>
> Hmmm. The problem I see is that it makes access to the full
> documentation contingent on connectivity to a possibility
[EMAIL PROTECTED] wrote:
I'm thinking that all documentation is better placed in
a wiki.
Hmmm. The problem I see is that it makes access to the full
documentation contingent on connectivity to a possibility ephemeral
external site. Maybe the solution is to incorporate wiki snapshots into
Eric Bohlman <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > http://www.sqlite.org/cvstrac/wiki?p=DateAndTimeFunctions
> > http://www.sqlite.org/lang_expr.html#corefunctions
> >
> > I will admit that the SQLite website is not particularly
> > well indexed for human browsing. But you
Bud Beacham <[EMAIL PROTECTED]> wrote:
> I cannot find any documentation
> on the SQLite documentation page that explains these functions.
> What other functions exist? What is the syntax? Where can they
> be used in SQL statements? Is there any documentation on these
> functions?
>
-users@sqlite.org, [EMAIL PROTECTED]
Subject: RE: [sqlite] Functions embedded in SQL statements
Date: Sun, 18 Jun 2006 14:50:23 -0700 (PDT)
Thank you, but I am not looking for C/C++ functions. I am using
Tcl. I am looking for the functions that appear to extend the
SQL syntax. I did not see
On 6/18/06, Bud Beacham <[EMAIL PROTECTED]> wrote:
My apologies if I have overlooked it.
I also had trouble finding them first few times, even though I knew
they were there somewhere.
Anyway, here's what you're looking for:
http://www.sqlite.org/lang_expr.html
--
Nemanja Corlija <[EMAIL
Bud Beacham <[EMAIL PROTECTED]> wrote:
> I have the book SQLite by Chris Newman and it has examples of
> functions embedded within SQL statements.
>
> For example on page 38 the ifnull() function is used.
>
> SELECT code, ifnull(due_date, 'Ongoing') FROM projects;
>
> Also, on page 81 the
Thank you, but I am not looking for C/C++ functions. I am using
Tcl. I am looking for the functions that appear to extend the
SQL syntax. I did not see either of the two functions I
mentioned (ifnull, strftime) on those pages.
bb
--- Christopher Smith <[EMAIL PROTECTED]> wrote:
> The C/C++
The C/C++ documentation can be found here:
http://sqlite.org/capi3ref.html#sqlite3_create_function
For those of us in the mortal category, various wrappers can make life
better. For example,
http://initd.org/pub/software/pysqlite/doc/usage-guide.html#creating-user-defined-functions
HTH,
I have the book SQLite by Chris Newman and it has examples of
functions embedded within SQL statements.
For example on page 38 the ifnull() function is used.
SELECT code, ifnull(due_date, 'Ongoing') FROM projects;
Also, on page 81 the strftime() function is used.
SELECT strftime('%m/%d/%Y',
14 matches
Mail list logo
