> 28.11.2011 23:08, Adriano dos Santos Fernandes wrote:
>
>> No. It happens with large varchar column. So it turns back to my
>> question: can we describe a column with a length we know will fit and
>> will have no side effects other than just being described different?
>
> I believe we can and we should. We had the same problem with PAD and
> AFAIR it has been resolved exactly this way. It's very convenient from
> the users POV.
While i agree with you about SUBSTRING, i think the much better solution
will be to allow to index COMPUTED BY columns. It allows to not compare
potentially complex expressions at optimize time and to not write exactly
same expressions in every query where such index is required.
Regards,
Vlad
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
