Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filename conflicts with composite primary keys #218

Open
tillilab opened this issue Sep 20, 2017 · 2 comments
Open

Filename conflicts with composite primary keys #218

tillilab opened this issue Sep 20, 2017 · 2 comments

Comments

@tillilab
Copy link

tillilab commented Sep 20, 2017

With some classes it happens that the same file name is used for different situations,

for example for class modTemplateVarTemplate and

        primary:
            - tmplvarid
            - templateid:

we can have

templateId: 4
tmplvarid: 15

that will have the same file name as record with:

templateId: 41
tmplvarid: 5

and as a result just the second situation is saved into gitify.

It could be useful to add a key separator or something like that,
thanks!


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@Mark-H
Copy link
Member

Mark-H commented Sep 20, 2017

Doesn't it put a hyphen dot in between the different parts of a composite key?

@tillilab
Copy link
Author

no, in the example above I have 415.yaml, but may be I'm missing something in configuration..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants