Alex, > Sean, if we limit ourself to only already opened files - we have no problems. > But there are places (like per-database config) where we are not sure does > file exist and if yes is it opened or not. For posix (where file ID exists no > matter is file opened or not) I'm currently using fast and precise by-ID > lookup, but if it cant be used - lookup by name is anyway needed nad > anyway used. If there is a way to generate stable (i.e. not depending upon > opened file or not) file ID on windows this must be done (sorry I've lost a > bit > in this discussion re. this issue).
The BY_HANDLE_FILE_INFORMATION FileIndex+Volume Serial Number properties do provide such a stable/unique file ID. It is the database config where there are likely to be significant issues in trying to relate filename to entries, due to config file encoding/locale characters and unknown/indeterminate filename case sensitivity. This is why I proposed to remove all per-database config values into individual database filename based config files. As it would remove most of these issue, by requiring the db<->config to follow a single/unified treatment (ie. by Windows itself). Sean ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
