From: "Vlad Khorsun" <[email protected]> > > What are you going to do, when databases will overflow this single > directory ? Buy new HDD ? Create new > directory and teach application to look for databases at two > "superaliases" ? >
As you pointed out, I can create a database for each year for the next hundred years. Doubtful, but theoretically possible. Even that won't fill up the directory because the data doesn't grow nearly as fast as hard drive space does. 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. User importing/exporting of data could be in a shared directory known as UserDataDir. Changing the location of these would become much easier just like it is now with database aliases. Not saying that just using standard aliases is a problem, just wondered if anyone else had situations where this might help and if there had been any discussion about it here. 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
