Hi! I started patch for longer metadata names and at the same time changing UNICODE_FSS to UTF8 in system tables and also changing the byte-limit to character-limit in them.
The major thing to discuss here is, what should be that character limit: 64, 128, other? Older than v4 tools (isql, gbak) connecting to v4 server should not work correctly only when dealing with longer than 31 characters names. ISQL commands that display things in columns (for example, SHOW TABLE) must be changed to print each item per line. There is the problem of how names (sqlname, relname, ownname, aliasname) will be represented in XSQLVAR which uses [32] arrays. By default (old clients) longer names will be truncated there. I do not think modern applications depends on these entries. It also lacks package name now and nobody noted. I treat this problem as low priority, but supposing we're going to do something to users of the legacy API access longer names, I think the best method is to have a function that obtains an IStatement from an isc_stmt_handle and read them with the new API. Adriano ------------------------------------------------------------------------------ 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
