RE: [sqlite] Re: "always-trim" - feature suggestion

> -Original Message- > From: Aristotle Pagaltzis [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 09, 2008 1:27 PM > To: sqlite-users@sqlite.org > Subject: [sqlite] Re: "always-trim" - feature suggestion > > > * Zbigniew Baniewski <[EMAIL PROTE

Re: [sqlite] Re: "always-trim" - feature suggestion

On Wed, Jan 09, 2008 at 08:27:13PM +0100, Aristotle Pagaltzis wrote: > Yes, actually, almost all requested and many implemented features > are by definition bloat. It depends on definition, I guess... ;) -- pozdrawiam / regards

[sqlite] Re: "always-trim" - feature suggestion

* Zbigniew Baniewski <[EMAIL PROTECTED]> [2008-01-09 18:15]: > On Wed, Jan 09, 2008 at 11:25:01AM -0500, Rob Sciuk wrote: > > and adding bloat will not contribute to its future success. > > Of course, any feature, which *you* aren't especially fond of, > you can describe as "bloat". Even the most

[sqlite] Re: "always-trim" - feature suggestion

* Zbigniew Baniewski <[EMAIL PROTECTED]> [2008-01-09 12:15]: > Keep your flamewar just to yourself, will you? I’m sorry if that’s all you saw in my mail. Regards, -- Aristotle Pagaltzis // -

Re: [sqlite] Re: "always-trim" - feature suggestion

On Wed, Jan 09, 2008 at 12:01:05PM +0100, Aristotle Pagaltzis wrote: > No, it doesn???t. And the next tiny feature like yours will not > cause a mess either. And the next one after that won???t cause a > mess either. Now keep addding tiny cannot-cause-a-mess features > for two years and the

[sqlite] Re: "always-trim" - feature suggestion

* Zbigniew Baniewski <[EMAIL PROTECTED]> [2008-01-07 03:35]: > 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.

Re: [sqlite] Re: "always-trim" - feature suggestion

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

Re: [sqlite] Re: "always-trim" - feature suggestion

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

Re: [sqlite] Re: "always-trim" - feature suggestion

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

Re: [sqlite] Re: "always-trim" - feature suggestion

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

[sqlite] Re: "always-trim" - feature suggestion

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