A new topic, 'what are the best practices to deal with partitioned tables in
liquibase?', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=30.new#new
The text of the topic is shown below:
Hi,
I'm new to liquibase, so my question may be answered somewhere already... What
are the best practices to deal with partitioned tables in liquibase? More
specifically I'm talking about oracle. Oracle's syntax for partitioned table
looks like
CREATE TABLE <TABLE> ( ... USUAL STAFF HERE... ) PARTITION BY <PARTITION SPEC>
What I like to see is to mark somehow staff in bold as context depended. So
when I create database in "test" context (singlenoded, nonclustered) all the
optimization staff of the create table expression is just ignored. I don't like
the idea of having two separate create table changelogs as this would introduce
place for errors...
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.
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
