Dmitry Yemanov wrote: > 03.06.2016 16:11, Adriano dos Santos Fernandes пишет: >> >> The major thing to discuss here is, what should be that >> character limit: 64, 128, other?
> I'm afraid the new limit should be 63 characters. 64 UTF-8 > characters means 256 bytes which does not fit BLR (string > length counter is single-byte there, max possible length is > 255 bytes). > Or we need to switch to longer BLR strings together with > longer context numbers, using a new BLR version. Do we have any real-life examples of why people want longer names? Something to target? There have been a few times where I would have liked a few extra characters for a procedure name (mostly because I tend to use name prefixes for various reasons, leaving less room for an actual name part). But it's rarely been much of a problem. So, in my case as one example, 63 would be absolutely fine. If this change is going to be lots of work then I'd rather see the effort put into a more comprehensive solution like the option 3 suggested by Dalton Calford. Most of the projects I have been involved with have tried to solve the localisation of object names in one way or another (even if, in many cases, the "localisation" has been only to localise programmer-speak into English ;-). Internalising that capability would be a nice thing to see and could offer other benefits as well, like being able to rename any object at any time without impact to the structure. -- Geoff Worboys Telesis Computing Pty Ltd ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
