On 03/14/2016 07:39 PM, Leyne, Sean wrote: > Alex, > >> The main problem with use of any kind of file ID is when create database is >> performed - file may not exist. > What kind of "use" of the file ID are you referring to? > > AFAIU, the file ID would only be used to identify if a db filename matches an > existing/already opened db file (the file id, not the filename string, would > become the "key" to uniquely identify file). Also, since the db file would > be open, it would not be possible for the file to be deleted.
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). But use of by name search if ID is unusable due to file not exists appears unavoidable. ------------------------------------------------------------------------------ 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
