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 level check contstraints.
The database is intended for data storage. Not data cleanup. This goes pretty
much for every commercial database out there as well.
Ken
Zbigniew Baniewski <[EMAIL PROTECTED]> wrote: 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 people - just by their intention - deliberately want to strip
*every* stored string? Wouldn't be this much smarter done such way?
> Or if you really have to have the pragma, it needs to be off by default.
Yes, that's what I'm suggesting: to add an option, which could change
default, just "for those about to trimming". It could (perhaps even should)
be "off" by default.
--
pozdrawiam / regards
Zbigniew Baniewski
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
