That is a great point. But it does help me slim down my app for
testing before deployment on another database
On Jan 7, 2008, at 5:21 PM, Scott Baker wrote:
Rick Langschultz wrote:
I think commercial database solutions have their place in the
market, and I don't think Richard looks bad in
Dennis Cote <[EMAIL PROTECTED]> wrote:
> I am wondering if anyone has already looked into why the SQLite
> amalgamation source file sqlite3.c repeats the same definitions and
> declarations so many times.
>
> For example the line
>
> #define SQLITE_VERSION "3.5.4"
>
> is repeated 9
I am wondering if anyone has already looked into why the SQLite
amalgamation source file sqlite3.c repeats the same definitions and
declarations so many times.
For example the line
#define SQLITE_VERSION "3.5.4"
is repeated 9 times at lines
456
73835
77835
87945
92304
96930
101250
On Jan 6, 2008 3:16 PM, Luc DAVID <[EMAIL PROTECTED]> wrote:
>
> Could you tell me the best way to achieve this under unbuntu and if I
> can optimise the compilation under Windows (the sqlite.dll size is quite
> important) ?
There are many ways. Most compilers allow you to define a string with
a
On Mon, Jan 07, 2008 at 03:29:21PM -0800, Darren Duncan wrote:
> The job of a DB isn't just storage of your data, but also to ensure
> that the data it stores is always conformant to the types and
> restrictions or business rules that you tell it applies to the data,
> so that the data can be
I think SQLite is an epochal leap in the development, dissemination, use
and support of databases in general. Richard has a product that moves
the whole field ahead. Sometimes other players are kicking and
screaming, but SQLite has still pushed them ahead because now their
product is competing
A "commodity" is something which is indistinguishable by brand (e.g.,
wheat, oil, frozen orange juice).
Calling SQLite a commodity is a misnomer.
Shawn M. Downey
MPR Associates
10 Maxwell Drive, Suite 204
Clifton Park, New York 12065
518-831-7544 (work)
518-763-6549 (cell)
-Original
At 9:14 PM +0100 1/7/08, Zbigniew Baniewski wrote:
On Mon, Jan 07, 2008 at 10:41:35AM -0800, Ken wrote:
In the spirit of the conversation the OP wants the DB to strip out white
space. I contend that this is the applications responsibility either as
DRH suggested by using proper sql
Rick Langschultz wrote:
I think commercial database solutions have their place in the market,
and I don't think Richard looks bad in this article. He simply created
something that needed to be created. When I am developing an application
that uses a database I first lay everything out on
I think commercial database solutions have their place in the market,
and I don't think Richard looks bad in this article. He simply created
something that needed to be created. When I am developing an
application that uses a database I first lay everything out on
whiteboard, then I write
On 1/7/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Says Brian Aker, Director of Architecture at MySQL AB:
>
>"SQLite has commoditized the entire low end of the database
> market out of existence."
>
> http://www.linuxworld.com/community/?q=node/2106
>
> --
makes you sound like a
[EMAIL PROTECTED] wrote:
Says Brian Aker, Director of Architecture at MySQL AB:
"SQLite has commoditized the entire low end of the database
market out of existence."
http://www.linuxworld.com/community/?q=node/2106
SWEET! Congrats on the commoditization of the low end database
market
Rael Bauer wrote:
Hi,
Can someone tell me how to select first n records from a query
(for e.g. Interbase has syntax: "rows 1 to n")
SELECT * FROM Table LIMIT 10;
or
SELECT * FROM Table LIMIT 15,10;
Shows 10 records, starting at the 15th.
--
Scott Baker - Canby Telcom
RHCE -
Rael Bauer wrote:
Can someone tell me how to select first n records from a query
select * from mytable limit 10;
Or, you can simply call sqlite3_step as many times as necessary, then
reset the statement.
See also OFFSET clause:
select * from mytable limit 10 offset 5;
Meaning, select
Hi,
Can someone tell me how to select first n records from a query
(for e.g. Interbase has syntax: "rows 1 to n")
Thanks
Rael
-
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
Says Brian Aker, Director of Architecture at MySQL AB:
"SQLite has commoditized the entire low end of the database
market out of existence."
http://www.linuxworld.com/community/?q=node/2106
--
D. Richard Hipp <[EMAIL PROTECTED]>
On Mon, Jan 07, 2008 at 10:41:35AM -0800, Ken wrote:
> In the spirit of the conversation the OP wants the DB to strip out white
> space. I contend that this is the applications responsibility either as
> DRH suggested by using proper sql expressions. Or by using a trigger. Or
> better yet by
hehe - check it out.
first comment: why no mention sqlite?
second comment: because its a trade magazine; consider their income
source.
third comment: thanks for name dropping SQL Anywhere in your article;
it beats sliced bread on mondays.
it couldn't be more perfect.
Ron Wilson, Senior
Igor,
Thanks for the correction on that, probably my wording "I don't think" in my
mind it meant I'm not sure... Lol, but thats another storry. Check constraints
are a feature I've not used in sqlite, so hence "I don't think", my mistake and
my applogies.
In the spirit of the conversation the
On Mon, Jan 07, 2008 at 11:37:25AM -0500, P Kishor wrote:
> As someone said, the most bugfree code is the one that didn't have to
> be written. While that is true from our perspective (let the db take
> care of it), it is also true from the perspective of the makers of the
> db (let the user take
speaking for myself, and projecting on the makers of SQLite...
On 1/7/08, Zbigniew Baniewski <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 07, 2008 at 03:59:52PM +, [EMAIL PROTECTED] wrote:
>
> > If you want to trim whitespace on insert, why not just say so:
> >
> >INSERT INTO table
On Mon, Jan 07, 2008 at 03:59:52PM +, [EMAIL PROTECTED] wrote:
> If you want to trim whitespace on insert, why not just say so:
>
>INSERT INTO table VALUES(trim(?),trim(?),trim(?));
>
> Instead of:
>
>INSERT INTO table VALUES(?,?,?);
Yes, yes - quite right. And exactly because of
Ken wrote:
Some commecial products have "check constraints" that allow you to
enable a check on a column that can be stored procedural code. That
could also be another way of keeping "non-trimmed" data out.
I don't think sqlite supports column level check contstraints.
Does too.
create
Ken <[EMAIL PROTECTED]> wrote:
>
> I don't think sqlite supports column level check contstraints.
>
SQLite has supported CHECK constraints since version 3.0.0,
released one year ago this coming Thursday.
On the other hand, a CHECK constraint cannot modify data
going into a table. It will only
Thats when a trigger or application code should be used.
Some commecial products have "check constraints" that allow you to enable a
check on a column that can be stored procedural code. That could also be
another way of keeping "non-trimmed" data out.
I don't think sqlite supports column
On Mon, 7 Jan 2008 09:21:38 -0500, "Samuel R. Neff"
<[EMAIL PROTECTED]> wrote:
>
>I got this when I tried to post a comment about missing SQLite in the
>article..
>
>"* You have been banned from posting. If you feel this is an error, please
>email [EMAIL PROTECTED] "
>
>I've never posted on eWeek
I got this when I tried to post a comment about missing SQLite in the
article..
"* You have been banned from posting. If you feel this is an error, please
email [EMAIL PROTECTED] "
I've never posted on eWeek before so this is upsetting.
Sam
---
We're
On Sun, Jan 06, 2008 at 07:39:55PM -0800, Darren Duncan wrote:
> I think that this would be a horrible thing if it were the default
> behaviour. A database needs to by default store and retrieve data
> pristine , so that people get out what they put in, not something
> else.
And when the
28 matches
Mail list logo
