03.06.2016 15:11, Adriano dos Santos Fernandes wrote:
> The major thing to discuss here is, what should be that character limit:
> 64, 128, other?
From MSDN: "SQL_MAX_IDENTIFIER_LEN(ODBC 3.0)
An SQLUSMALLINT that indicates the maximum size in characters that the
data source
supports for user-defined names. An FIPS Entry level–conformant driver will
return at
least 18. An FIPS Intermediate level–conformant driver will return at least
128."
I think that 128 is a good compromise.
> 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.
That's ok, but make sure that they are truncated to whole character, not
just byte.
> 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.
I'd prefer to introduce XSQLDA version 2.
--
WBR, SD.
------------------------------------------------------------------------------
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
