Liquibase Community Forum
2010-12-21 13:06:59 UTC
A new topic, 'Extend the concept to NOSQL database', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=851.new#new
The text of the topic is shown below:
Hi,
I'm used to liquibase to generate and maintain my DB.
I would not do it another way anymore.
I try to create generic code I can easilly move to a new DB brand if needed.
But recently I was facing a problem: I have to build an application with Google App Engine.
After some investiagation... I discover that my way of working don't change a lot in the application.
I "only" need to adapt some part of the code to use the BigTables of Google.
But... so far I know... impossible to reuse liquibase to generate the "repository".
The same if I want to patch the Data structure... How to apply patches without liquibase.
I have the feeling I have to reinvent the weel.
In a certain point of view, the problems are similar for BigTable than for DB.
So, why not include this functionnality to liquibase ?
Thanks for response.
Kind regards,
Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.
You can see it at
http://liquibase.org/forum/index.php?topic=851.new#new
The text of the topic is shown below:
Hi,
I'm used to liquibase to generate and maintain my DB.
I would not do it another way anymore.
I try to create generic code I can easilly move to a new DB brand if needed.
But recently I was facing a problem: I have to build an application with Google App Engine.
After some investiagation... I discover that my way of working don't change a lot in the application.
I "only" need to adapt some part of the code to use the BigTables of Google.
But... so far I know... impossible to reuse liquibase to generate the "repository".
The same if I want to patch the Data structure... How to apply patches without liquibase.
I have the feeling I have to reinvent the weel.
In a certain point of view, the problems are similar for BigTable than for DB.
So, why not include this functionnality to liquibase ?
Thanks for response.
Kind regards,
Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.