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

New NamingStrategy for Querydsl SQL #55

timowest opened this issue Nov 22, 2011 · 1 comment

New NamingStrategy for Querydsl SQL #55

timowest opened this issue Nov 22, 2011 · 1 comment


Copy link

@timowest timowest commented Nov 22, 2011

A new NamingStrategy based on the default naming strategy with improved FK name generation.

The naming on db level would be fk__


tables user and company
user has fk_company_users foreign key to referencing company via company_id

generated fk names in meta model are

class User { company: Fk }
class Company { users: InvFK }

other examples

Order / Row : fk_order_rows
Category / Events : fk_category_events

The risk of name clashes is bigger with this kind of namingstrategy, but the constraint names are intuitive and the resulting fk / invFk names in the model as well.

timowest added a commit that referenced this issue Nov 26, 2011
Copy link
Member Author

@timowest timowest commented Dec 12, 2011

Released in 2.3.0

@timowest timowest closed this Dec 12, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant