>> What’s the point of the rename? It seems to only break existing code >> and documentation. >> > aliases.conf name does not reflect what for this file can be used in > fb3. In addition to defining aliases for databases it now supports > per-database configuration parameters. We (I and Dmitry) failed to > invite better name than databases.conf. If you have ideas, you are welcome.
I'm not sure if it is a good idea to have those per-database configurations in one central place. So when you move a database to another server you have to copy-and-paste those things to the other server. What about having a pair of files: mydb.fdb mydb.conf Where mydb.conf contains the per-database configuration? In this case, all you need to do is copy or move both files together. What about backups? Will GBAK backup and restore these settings so they don't get lost? Regards Stefan ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
