On 02/05/2016 01:10 PM, Jonathan Beluch wrote:
Just realized #4 isn't so simple either as the comparison is always done
by name.
if this is a one-time migration why is autogenerate needed at all?
Just write out the migration for all the constraints either manually or
using your own one-off
On 02/05/2016 12:46 PM, Jonathan Beluch wrote:
Hi, I have an existing pg database where I'd like to get the names in
order according to a new naming_convention. However, dropping and
recreating lots of indexes is obviously a bad idea.
I've coded RenameConstraintOp and RenameIndexOp along with
Just realized #4 isn't so simple either as the comparison is always done by
name.
On Friday, February 5, 2016 at 10:46:14 AM UTC-7, Jonathan Beluch wrote:
>
> Hi, I have an existing pg database where I'd like to get the names in
> order according to a new naming_convention. However, dropping and
Hi, I have an existing pg database where I'd like to get the names in order
according to a new naming_convention. However, dropping and recreating lots
of indexes is obviously a bad idea.
I've coded RenameConstraintOp and RenameIndexOp along with the dispatch
functions. I'm trying to figure out
