Adriano dos Santos Fernandes wrote: > On 03/06/2016 10:35, Geoff Worboys wrote: >> This is not a request, I am just asking whether the option >> has been considered as a way of maintaining backward >> compatibility. > Not considered nor will.
> No reason to introduce such things for so small and easy to > fix problem with is not even a problem if they do not use > longer names when they can't support. Can I suggest then, that you implement a database option and/or a server option that controls the acceptance of long metadata names. Databases could upgrade with the option set to deny long names. This would help to ensure that people don't get themselves in the situation of accidentally shutting out their existing database tools (eg: submitting a script with an unnoticed extra character in a name). Indeed, such an option could let developers manage the maximum length of the names they want to support. You could implement support for 255 in the metadata tables, but default the limit to 128 for new databases ... or something like that. Just a thought. -- 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
