On 03/11/2016 06:59 PM, Leyne, Sean wrote: > >> When 2 different files will be opened as same dbb in SS that will be >> definitely >> not very convenient. > But couldn't that be addressed by having SS open database files using > "Exclusive Read/Write" access, instead of "Shared Read/Write" needed by > Classic? > > The OS knowns if the file is the same or not, regardless of the case > spelling...
OS certainly knows, but when we attach to database SAMPLE.fdb we look in the list of opened databases - do we already have such database opened? And if we use case-insensitive comparison of file names and have sample.fdb already attached we will decide that we have one more attachment to it, i.e. invalid database file will be used. In the best case user will not find required objects in it or will not have access rights to them. In the worst case he will select wrong data, modify data in invalid way, etc. I expect a question - why will anyone have files SAMPLE.fdb and sample.fdb in same directory? Very easy due to some mistake (but files are expected to be different) - OS has no problems storing files with such names. But sometimes it may even be not a mistake but an expected method (big SAMPLE and little sample in our case). Why not in OS that has this feature documented? For example, on the first page of `make' manual we can read: If no -f option is present, make will look for the makefiles GNUmakefile, makefile, and Makefile, in that order. For one regularly working with such system that style of names is good and convenient. ------------------------------------------------------------------------------ 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=278785111&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
