Sqlite has Big names. May be this should be
showcased at the sidebar on the front page.
Does it need any other brand building activity?
Atleast we got a better with those names.
regards
ragha
**
This email
John Stanton wrote:
This also is an anecdote from some time back. As we were signing a
fairly significant software contract with a large organization their
manager told us "You guys know nothing about marketing. Your
presentation was unprofessional, no glossy brochures, no audio visuals
and
Zbigniew Baniewski wrote:
On Sat, Dec 15, 2007 at 12:48:44PM -0500, Robert L Cochran wrote:
I did a poor job of explaining this issue. GCC builds of 3.5.4 seem to
fail. I've sent Richard a bunch of log files comparing source code
builds of versions 3.5.3 and 3.5.4 showing what I believe are
On Sat, Dec 15, 2007 at 12:48:44PM -0500, Robert L Cochran wrote:
> I did a poor job of explaining this issue. GCC builds of 3.5.4 seem to
> fail. I've sent Richard a bunch of log files comparing source code
> builds of versions 3.5.3 and 3.5.4 showing what I believe are symptoms
> of the alleg
> This also is an anecdote from some time back. As we were
> signing a fairly significant software contract with a large
> organization their manager told us "You guys know nothing
> about marketing. Your presentation was unprofessional, no
> glossy brochures, no audio visuals and we would no
This is not a link issue, but a compiler one. SQLite is ANSI C, so you
should compile it with gcc. It will still be usable within your C++
library/project, as sqlite3.h qualifies all functions extern "C".
For example, given a C++ file main.cpp:
#include
int main()
{
sqlite3* db;
sqlite3
> My intent is to provide complete detailed technical
> information about SQLite, including its limitations and
> faults, and honest comparisons and even recommendations of
> other products (including, but not limited to DeviceSQL). My
> intent is to avoid sophistry, misrepresentation,
> exa
Sorry.. meant English is NOT my primary language :)
Daniel Önnerby wrote:
I figure I'll keep it short since it's only for the FAQ.
English is my primary language, but here my suggestion:
Question: Does SQLite handle unicode?
Short answer: Yes!
Answer:
SQLite handles unicode very well. SQLite
Hi there,
I have compiled version 3.5.2 of the amalgamation in C without any errors or
warnings but when I am trying to do the same in C++ using g++ I keep getting
lots of errors and warnings. I have -ldl -lpthread in Makefile and running
Fedora Core 6.
Here are some reported errors and warnin
The documentation is obscure on that point.
Than you.
Brad Stiles wrote:
>
>> I got a BOOLEAN field. It's defined: NOT NULL.
>>
>> when a new record is inserted, how to put a Boolean Default Value
>> as FALSE?
>
> By reading the documentation.
>
> http://www.sqlite.org/lang_createtable.html
Thank you.
Igor Tandetnik wrote:
>
> Runspect <[EMAIL PROTECTED]> wrote:
>> I got a BOOLEAN field. It's defined: NOT NULL.
>>
>> when a new record is inserted, how to put a Boolean Default Value as
>> FALSE?
>
> SQLite doesn't have a dedicated boolean type. You just store them as
> integer, z
Runspect <[EMAIL PROTECTED]> wrote:
I got a BOOLEAN field. It's defined: NOT NULL.
when a new record is inserted, how to put a Boolean Default Value as
FALSE?
SQLite doesn't have a dedicated boolean type. You just store them as
integer, zero for false and nonzero for true. So make it
create
> I got a BOOLEAN field. It's defined: NOT NULL.
>
> when a new record is inserted, how to put a Boolean Default Value
> as FALSE?
By reading the documentation.
http://www.sqlite.org/lang_createtable.html
http://www.sqlite.org/lang_createtrigger.html
Brad
I got a BOOLEAN field. It's defined: NOT NULL.
when a new record is inserted, how to put a Boolean Default Value as FALSE?
Thanks.
--
View this message in context:
http://www.nabble.com/BOOLEAN-DEFAULT-VALUE-tp14361417p14361417.html
Sent from the SQLite mailing list archive at Nabble.com.
--
14 matches
Mail list logo
