Posted by moshe weitzman on July 18, 2011 at 3:59pm
In some cases, it would be really cool if the DB dump in the archive were in DBTNG format. Thats a new format which can be imported by SQlite, MySQL, Postgres, and contrib DBTNG drivers. See http://drupal.org/project/dbtng_migrator
I think we should call this 'driver' DBTNG in our Manifest.ini.
Do folks think this useful? Would Gardens, Pantheon, etc. be willing to support this during export and/or import?
Comments
Would it be able to handle
Would it be able to handle someone's completely hacked up, "customized" database? Potential issues aside, who wouldn't want that sort of portability?
Yes, hacked up code and DB
Yes, hacked up code and DB would export fine, as long as the column types are supported by DBTNG. Not too hard to add custom column types here.
Yes, I think people do want platform mobility. This discussion is mainly about those "potential issues". I think the main question mark here is about demand. When it comes down to it, Drupal sites are powered by MySQL with little deviation. Wondering if others can add alternate ideas on that. I do think portability might benefit folks who want to experiment on Postgres and SQLite.
One issue is that importing a platform-independant dump could take a bit longer than a platform-specific one since it has to run through Drupal, instead of Db native import command.
+1
The exact specifics of DBTNG escape me (except knowing that it's part of the new db layer of D7). Personally, I'm currently dealing with the discrepancies related to the ways modules and web hosts each implement Backup, Restore, Migrate and Cloning functionality.
While the stuff I'm working with is d6 (where DBTNG does not apply), I'm still planning to migrate to d7 in the near-future. The d6-d7 upgrade path itself is painful yet having the ability to archive a complete Drupal site consistently regardless of Drupal core version, would be nice.
Just knowing that DBTNG, while new, is a more flexible file format sounds good to me. Perhaps this will lower the step-in height for those moving/upgrading to a Gardens, Pantheon, Acquia, etc. hosting environment?
Thoughts?
_rs
+1
in the first place this would make it possble to develop on a sqlite db and directly push to masql, right? would be cool.
This is also a tool against obsolescence
This is also a tool against obsolescence (independence of vendor/version). Useful in a future to migrate sites stalled in (very) old versions of db server or preserve long-term access to backups.