Adriano dos Santos Fernandes wrote: > Em 03/06/2016 23:30, Geoff Worboys escreveu: >> 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. >>
> Agree, but this should be an option in databases.conf, and by > default it should allow the max. possible length. I'd prefer to see it in the database. I see it as a behavioral attribute of the database, how it should be seen by all servers and not just some particular server. I guess databases.conf will inevitably carry some behavioral attributes eventually (some things that just have to overlap with server configurations), but I think that should be avoided when alternatives are viable. -- 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
