• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Is it ok to drop the foreign keys created by EJB 3 on the database?

 
Ranch Hand
Posts: 551
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Can you please let me know what will happen if I delete the foreign keys created by EJb 3 in my database?

Thanks
 
Bartender
Posts: 2661
19
Netbeans IDE C++ Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

raminaa niilian wrote:Hi,

Can you please let me know what will happen if I delete the foreign keys created by EJb 3 in my database?

Thanks

Drop the columns, or drop the constraints?
 
raminaa niilian
Ranch Hand
Posts: 551
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

The constraint and not the columns.

Thanks
 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

raminaa niilian wrote:
The constraint and not the columns.

Thanks



I'm not sure about the scenario. But if you drop the constraint, the jpa won't be able to retrieve the attribute as an instance of the entity the foreign key references. ie, entity A has an attribute person which is an int that references to the Id of entity Person. If the foreign key is lost, person will be an int instead of being an instance of Person. Is that what you mean?
 
raminaa niilian
Ranch Hand
Posts: 551
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

alice zhu wrote:

raminaa niilian wrote:
The constraint and not the columns.

Thanks



I'm not sure about the scenario. But if you drop the constraint, the jpa won't be able to retrieve the attribute as an instance of the entity the foreign key references. ie, entity A has an attribute person which is an int that references to the Id of entity Person. If the foreign key is lost, person will be an int instead of being an instance of Person. Is that what you mean?




Do you mean that JPA uses the FK themselves to make multiplicity relations? I think they use the related database column to do that and not the FK itself. My doubt is that dropping the fks may cause other unexpected problems.
 
reply
    Bookmark Topic Watch Topic
  • New Topic