From: "Vlad Khorsun" <[email protected]> >> >> However, it would be useful, IMO, to have an alias for directories so >> that >> conceptually, you could separate entire functionalities. For instance, >> the >> main databases reside in an alias directory called MainDataDir. Backups >> could be performed to the BackupDataDir. > > aliases for backup files ? Oh... >
Sure. All my nightly backups for a particular application go to the same backup directory. That directory gets backup up by the system, just as it should be done. Having an aliased backup directory would give me the same flexibility as connecting to databases that are commonly located. >> User importing/exporting of data >> could be in a shared directory known as UserDataDir. > > Seems you want that Firebird implement solution for your applied issue. > Not really, just listing some of the possibilities that it could be used for. >> Changing the location >> of these would become much easier just like it is now with database >> aliases. > > Let me guess how you going to use this super-aliases : > > a) create entry at aliases.conf for common folder for historical databases > : > > databases = c:\archive\databases > > b) Application have built-in (or configurable) knowledge about this > super-alias > > c) Application want to work with database of year NNN. It should open it > as > databases:yearNNN > > d) in Year 2015 space on disk C: is over and you want to add second > super-alias, say > > databases2 = d:\archive\databases > > e) Aplication should be changed to take it into account !!! > > > If you pre-create *aliases* for databases : > > year2010 = c:\archive\databases\year2010.fdb > year2011 = c:\archive\databases\year2011.fdb > year2012 = c:\archive\databases\year2012.fdb > year2013 = c:\archive\databases\year2013.fdb > year2014 = c:\archive\databases\year2014.fdb > year2015 = c:\archive\databases\year2015.fdb > year2016 = c:\archive\databases\year2016.fdb > > and at some point of time you are out of disk space on drive C, all you > need to do is > to change few aliases and don't touch application : > > year2015 = D:\archive\databases\year2015.fdb > year2016 = D:\archive\databases\year2016.fdb > I didn't say it would work for everyone or every situation. Does anything? However, as with everything else in my programs, I would have already built in a settings form which would be used to control that for the administrator just as I have now for working with the current format. In general, I try to build in full control so that outside help isn't needed for simple changes like this. For instance, my main database contains a table listing each fiscal archive database created. That makes it easy for a generic loop to search for information through any time period. If I used aliases for those, which I don't currently, I would add an alias field to that table. If there were a directory alias I could use, I would put that in the field instead of the database alias. I am going to convert to using only aliases in the very near future and using just such a field for pointing to each database for the exact reason you specified, disk space issues and possible location changes. The recent discussion about providing alias configuration through the API held my interest since now it has to be done using separate programs or direct administrator control by logging into the server. Woody (TMW) ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
