Some of the correspondents seem to have lost track of the meaning of
"Open Source". They have the source code and can build their own
version which trims, slashes or even burns. They certainly do not have
to inflict their particular needs or preferences on the whole user
community.
I am
On Wed, Jan 09, 2008 at 07:16:27PM +, [EMAIL PROTECTED] wrote:
> Puneet also speaks for me on this matter.
I'm glad, dr. Hipp, you haven't found my answer as offensive or abusive - of
course, as I wrote, it was just a proposal, an idea - not any "demanding".
But to know your opinion about
On Wed, Jan 09, 2008 at 11:12:42AM -0800, James Dennett wrote:
> To take an example (and I apologize for it being from your message, but
> that's a convenient place): when you write "I ended the discussion
> *yesterday* already", it's easy for me to take that as being rude
> because it implies
"P Kishor" <[EMAIL PROTECTED]> wrote:
> fwiw, Zbigniew, I did not consider you rude or argumentative, but yes,
> this thread would have been "trimmed" a lot earlier after pretty much
> the very first "request for implementation."
>
> I hope you won't be put off by any perceived "hostility." No
> -Original Message-
> From: Zbigniew Baniewski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 09, 2008 10:57 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] "always-trim" - feature suggestion
>
> On Wed, Jan 09, 2008 at 07:15:52PM +010
fwiw, Zbigniew, I did not consider you rude or argumentative, but yes,
this thread would have been "trimmed" a lot earlier after pretty much
the very first "request for implementation."
I hope you won't be put off by any perceived "hostility." No one wants
to be that way. Your comments,
On Wed, Jan 09, 2008 at 07:15:52PM +0100, Kees Nuyt wrote:
> It's a culture thing. In Eastern Europe this is the normal way
> of reasoning, and isn't considered rude (my girlfriend is
> Latvian from Russian parents, so I have some experience with
> this kind of culture shock).
I'm afraid, I
On Wed, Jan 09, 2008 at 12:04:54PM -0600, Fred Williams wrote:
> range beginning with MySQL and ending with Oracle. I do not beat a dead
> horse trying to get the entire SQLite world and Dr. Hipp in particular
> to "see it MY way." Give it up and look for a more feature rich DB and
> leave us
On Wed, 9 Jan 2008 08:57:18 -0800 (PST), Ken
<[EMAIL PROTECTED]> wrote:
> I think your being argumentative,
> disrespectful and just plain rude.
I don't think Zbigniew does that on purpose.
It's a culture thing. In Eastern Europe this is the normal way
of reasoning, and isn't considered rude
> -Original Message-
> From: Zbigniew Baniewski [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 09, 2008 11:08 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] "always-trim" - feature suggestion
>
>
> On Wed, Jan 09, 2008 at 11:25:01AM -050
On Wed, Jan 09, 2008 at 08:57:18AM -0800, Ken wrote:
> After reading your response to DRH, I think your being argumentative,
> disrespectful and just plain rude.
Thanks, I love you too.
--
pozdrawiam / regards
On Wed, Jan 09, 2008 at 11:25:01AM -0500, Rob Sciuk wrote:
> You know, I believe that an "embedded" SQL has a philosophy which is
> inherently minimalist.
...yes, I know.
> Your request specifically goes against the
> philosophy of what SQLite was designed to be. DRH is working hard to
>
It's rather hard to say, if really just "single". SQLite, as I understood,
has many users; just three of them were "against", until this time.
Who knows, which of the existing features are used by how many users?
Yesterday one of them wrote, that (if I properly understood) he appreciates
On Wed, 9 Jan 2008 14:33:40 +0100, Zbigniew Baniewski
<[EMAIL PROTECTED]> wrote:
>On Wed, Jan 09, 2008 at 12:51:16PM +, [EMAIL PROTECTED] wrote:
>
>> > Why not have a possibility to make it default
>> > behaviour of the SQL-engine itself, just by
>> > using one "pragma"?
>> >
>> > 1. It'll
On Wed, 9 Jan 2008, Zbigniew Baniewski wrote:
On Wed, Jan 09, 2008 at 12:51:16PM +, [EMAIL PROTECTED] wrote:
Why not have a possibility to make it default
behaviour of the SQL-engine itself, just by
using one "pragma"?
1. It'll make my code shorter.
But it makes the SQLite core code
On Wed, Jan 09, 2008 at 12:51:16PM +, [EMAIL PROTECTED] wrote:
> > Why not have a possibility to make it default
> > behaviour of the SQL-engine itself, just by
> > using one "pragma"?
> >
> > 1. It'll make my code shorter.
>
> But it makes the SQLite core code larger. Why should the the
>
Zbigniew Baniewski <[EMAIL PROTECTED]> wrote:
>
> Why not have a possibility to make it default
> behaviour of the SQL-engine itself, just by
> using one "pragma"?
>
> 1. It'll make my code shorter.
But it makes the SQLite core code larger. Why should the the
SQLite core be enlarged for 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 <[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 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
At 3:28 AM +0100 1/7/08, Zbigniew Baniewski wrote:
I think, that it sometimes could be useful as secondary protection: a
feature (perhaps another "pragma"?), which will cause stripping the spaces
from beginning and end of every inserted string. But perhaps even not just
only as "secondary"?
I think, that it sometimes could be useful as secondary protection: a
feature (perhaps another "pragma"?), which will cause stripping the spaces
from beginning and end of every inserted string. But perhaps even not just
only as "secondary"?
Yes, usually it's done at application level; I was
25 matches
Mail list logo
