Hi. > IMHO, forcing the database(schema)/directory relationship is the bigger > problem. > Not coming from the deployment space, though...
Being a sysadmin myself, i dont like much the idea of symlink files around to workaround this limitation and today volume management capabilities in software/hardware make it unnecessary. As a long shot i think the best solution is to think of tablespaces as a separate entities to storage schemas. With that in mind you can add some statements to do basic management directly in SQL, and also unify the storage engine treatment of tablespaces. -- Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. -- Antoine de Saint Exupéry _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
