I know you can set the connection parameter (CON=...) and SQLAnywhere will show it in connection_property('name'). But if you don't set it at connection time, SQLAnywhere shows something like SQL_DBC_16544f00.
Is it safe to say that SQLAnywhere creates a complete random and unique name for each connection? Even in two different databases?
I would like to know how SQLA creates this random name. Best
asked 01 Dec '11, 13:57
It is just a hex representation of a pointer to an object allocated for the connection inside dblib. It is not guaranteed to be very random. In fact, two identical apps are very likely to get the same connection name. No two connections that are open at the same time and established from a single process will have the same connection name; however, the name can be reused if the app disconnects and reconnects.