Timestamp-Based Versions about cdeploy HOT 4 CLOSED

@bradgignac, can you point me to some documentation about this timestamp-based versioning system? I don't have a history with Ruby on Rails so I'm unfamiliar. I'm happy to consider it after doing a little investigation. Thanks!

from cdeploy.

@BryanSD http://edgeguides.rubyonrails.org/active_record_migrations.html#creating-a-standalone-migration

from cdeploy.

I took a quick look at this and I think it'll actually work with cdeploy as-is. Currently, the filename is split on underscores and the first portion is converted to an integer. We then simply sort the integers to get the order in which to apply the migration scripts.

If your migration files took the form of 20150317154512_add_table.cql and 20150317144556_add_column.cql that'd work, no? Of course that doesn't help if any conflicting CQL statements are contained within two files but you'd have that problem either way.

Maybe it'd be beneficial to add a tip around this to the documentation?

from cdeploy.

Closing since this may not be a problem and seems to be abandoned. Happy to reopen if the need arises.

from cdeploy.