On 29-11-2011 05:56, Dmitry Yemanov wrote: > 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. >
This is also my opinion. "Descripted" type is not very important, so we may do somethings different than is understood in the standard. And we didn't had important compatibility problems even with more drastic change, like one who changed result of SUBSTRING(BLOB) from varchar to blob. Adriano ------------------------------------------------------------------------------ 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
