On 07/17/12 11:41, Paul Reeves wrote: > On Tuesday 17 Jul 2012 10:58:37 Alex Peshkoff wrote: >> On 06/21/12 11:33, Dmitry Yemanov wrote: >>> 21.06.2012 11:20, Alex Peshkoff wrote: >>>> Both places. A lot of firebird.conf parameters can be used in aliases in >>>> order to have different config per database. >>> Maybe we should think about renaming aliases.conf to something like >>> databases.conf to better reflect both its original (custom database >>> naming) and new (database specific configuration) semantics? >> Renaming has both pluses (mentioned by you) and minuses (people, who do >> not need per-DB config, but want to manage aliases, will find it as a >> minimum strange). For posix systems solution is trivial - add symlink. >> But no idea what to do with windows in that case. >> > Why not just include both files (if they exist), with the contents of > databases.conf having precedence over aliases.conf? Obviously we can document > aliases.conf as deprecated.
It's almost unreal to fallback to aliases.conf. When we install FB we will anyway create databases.conf in $FbRoot. I.e. even if one copies his old aliases.conf it will not work cause databases.conf also exists. I.e. that guy will have to manually remove databases.conf to access old file. And in that case I see no difference between removing databases.conf and renaming aliases.conf to databases.conf. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
