On Wed, Nov 18, 2015 at 11:23:11PM -0500, Mike Bayer wrote:
> if you change your naming convention, then that would show up as a bunch
> of brand new constraints in the model and a whole bunch of constraints
> removed in the model, so in theory would produce a lot of add constraint
> / drop
On 11/19/2015 04:01 AM, Chris Frey wrote:
> On Wed, Nov 18, 2015 at 11:23:11PM -0500, Mike Bayer wrote:
>> if you change your naming convention, then that would show up as a bunch
>> of brand new constraints in the model and a whole bunch of constraints
>> removed in the model, so in theory
In the alembic documentation, there is an entire page devoted to naming
constraints:
http://alembic.readthedocs.org/en/latest/naming.html
So I assumed that if constraints had a naming scheme defined, then
those names would be detected if changed.
My specific use case is as follows. My
On 11/18/2015 06:41 PM, Chris Frey wrote:
> In the alembic documentation, there is an entire page devoted to naming
> constraints:
>
> http://alembic.readthedocs.org/en/latest/naming.html
>
> So I assumed that if constraints had a naming scheme defined, then
> those names would be
