29.06.2012 19:27, Paul Vinkenoog wrote: >> - Case for UUID_TO_CHAR will not be changed as this will be backward >> incompatible. So we live with it, everyone could use LOWER. > > Too bad, I would personally have preferred to see it changed. But I realise > that this could break some existing code. Maybe a convenience function > UUID_TO_LOCHAR would be nice?
I'd stay with a need for LOWER, unless other issues would force us to have UUID_TO_CHAR2 (whatever it is named). >> Also I guess there is still time to commit it for 2.5.2, as otherwise >> nothing of this makes sense. > > Quite agreed. Absolutely agreed. We should have a final point on this subject before v2.5.2 goes public. Dmitry ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
