JHipster - import-jdl - Field has jhi_ added to name
up vote
0
down vote
favorite
I've created a new JHipster project, used JDL Studio to create a .jh schema file, and added it to the project. After doing the import-jdl and project rebuild, one of my fields has had 'jhi_' added to the name.
Can anyone shed light on this?
I'm guessing maybe I've used a reserved word. But I can't find a list of JHipster's reserved words, if there are any.
Thanks in advance.
Full details:
JHipster generation options: monolithic, not using Registry, JWT authentication, MySQL database, Hazelcast cache implementation, 2nd level cache enabled, Gradle, WebSockets, Angular, SASS, no internationalisation, Protractor, no other generators.
The field affected is the cost field in this JDL definition:
entity Product {
description String required maxlength(100)
price BigDecimal required min(0)
cost BigDecimal required min(0)
weight Integer min(0)
barcode String required maxlength(13)
shelfLife Integer min(0)
isActive Boolean required
lastModified Instant required
}
And its relationships:
relationship OneToMany {
Product to Shelf{product (description) required},
Product to TransactionItem{product (description) required}
}
It appears in the MySQL database, and in all generated code, as jhi_cost
All other fields are appearing exactly as I expect.
java mysql jhipster jdl
add a comment |
up vote
0
down vote
favorite
I've created a new JHipster project, used JDL Studio to create a .jh schema file, and added it to the project. After doing the import-jdl and project rebuild, one of my fields has had 'jhi_' added to the name.
Can anyone shed light on this?
I'm guessing maybe I've used a reserved word. But I can't find a list of JHipster's reserved words, if there are any.
Thanks in advance.
Full details:
JHipster generation options: monolithic, not using Registry, JWT authentication, MySQL database, Hazelcast cache implementation, 2nd level cache enabled, Gradle, WebSockets, Angular, SASS, no internationalisation, Protractor, no other generators.
The field affected is the cost field in this JDL definition:
entity Product {
description String required maxlength(100)
price BigDecimal required min(0)
cost BigDecimal required min(0)
weight Integer min(0)
barcode String required maxlength(13)
shelfLife Integer min(0)
isActive Boolean required
lastModified Instant required
}
And its relationships:
relationship OneToMany {
Product to Shelf{product (description) required},
Product to TransactionItem{product (description) required}
}
It appears in the MySQL database, and in all generated code, as jhi_cost
All other fields are appearing exactly as I expect.
java mysql jhipster jdl
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've created a new JHipster project, used JDL Studio to create a .jh schema file, and added it to the project. After doing the import-jdl and project rebuild, one of my fields has had 'jhi_' added to the name.
Can anyone shed light on this?
I'm guessing maybe I've used a reserved word. But I can't find a list of JHipster's reserved words, if there are any.
Thanks in advance.
Full details:
JHipster generation options: monolithic, not using Registry, JWT authentication, MySQL database, Hazelcast cache implementation, 2nd level cache enabled, Gradle, WebSockets, Angular, SASS, no internationalisation, Protractor, no other generators.
The field affected is the cost field in this JDL definition:
entity Product {
description String required maxlength(100)
price BigDecimal required min(0)
cost BigDecimal required min(0)
weight Integer min(0)
barcode String required maxlength(13)
shelfLife Integer min(0)
isActive Boolean required
lastModified Instant required
}
And its relationships:
relationship OneToMany {
Product to Shelf{product (description) required},
Product to TransactionItem{product (description) required}
}
It appears in the MySQL database, and in all generated code, as jhi_cost
All other fields are appearing exactly as I expect.
java mysql jhipster jdl
I've created a new JHipster project, used JDL Studio to create a .jh schema file, and added it to the project. After doing the import-jdl and project rebuild, one of my fields has had 'jhi_' added to the name.
Can anyone shed light on this?
I'm guessing maybe I've used a reserved word. But I can't find a list of JHipster's reserved words, if there are any.
Thanks in advance.
Full details:
JHipster generation options: monolithic, not using Registry, JWT authentication, MySQL database, Hazelcast cache implementation, 2nd level cache enabled, Gradle, WebSockets, Angular, SASS, no internationalisation, Protractor, no other generators.
The field affected is the cost field in this JDL definition:
entity Product {
description String required maxlength(100)
price BigDecimal required min(0)
cost BigDecimal required min(0)
weight Integer min(0)
barcode String required maxlength(13)
shelfLife Integer min(0)
isActive Boolean required
lastModified Instant required
}
And its relationships:
relationship OneToMany {
Product to Shelf{product (description) required},
Product to TransactionItem{product (description) required}
}
It appears in the MySQL database, and in all generated code, as jhi_cost
All other fields are appearing exactly as I expect.
java mysql jhipster jdl
java mysql jhipster jdl
edited yesterday
Spara
2,07711233
2,07711233
asked Nov 22 at 2:25
B Houliston
32
32
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
COST is listed as a reserved word for Oracle in the generator (see oracle.js) so it gets prefixed when you select Oracle as target database. The prefix is globally configurable using --jhi-prefix
command line option. You say you use MySQL so it's a bit surprising as COST is not included in mysql.js so maybe there's a bug you should report on github with your project setup.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
COST is listed as a reserved word for Oracle in the generator (see oracle.js) so it gets prefixed when you select Oracle as target database. The prefix is globally configurable using --jhi-prefix
command line option. You say you use MySQL so it's a bit surprising as COST is not included in mysql.js so maybe there's a bug you should report on github with your project setup.
add a comment |
up vote
0
down vote
accepted
COST is listed as a reserved word for Oracle in the generator (see oracle.js) so it gets prefixed when you select Oracle as target database. The prefix is globally configurable using --jhi-prefix
command line option. You say you use MySQL so it's a bit surprising as COST is not included in mysql.js so maybe there's a bug you should report on github with your project setup.
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
COST is listed as a reserved word for Oracle in the generator (see oracle.js) so it gets prefixed when you select Oracle as target database. The prefix is globally configurable using --jhi-prefix
command line option. You say you use MySQL so it's a bit surprising as COST is not included in mysql.js so maybe there's a bug you should report on github with your project setup.
COST is listed as a reserved word for Oracle in the generator (see oracle.js) so it gets prefixed when you select Oracle as target database. The prefix is globally configurable using --jhi-prefix
command line option. You say you use MySQL so it's a bit surprising as COST is not included in mysql.js so maybe there's a bug you should report on github with your project setup.
answered Nov 22 at 7:24
Gaël Marziou
9,45722432
9,45722432
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423050%2fjhipster-import-jdl-field-has-jhi-added-to-name%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown