Foreign keys are good for making sure your data is consistant, for example you cant reference a bank account that does not exist. They are also good for defining delete rules, such as if this order is deleted, make sure all orderrows are deleted too. Correctly defined, they also speed up searching over multiple tables (if needed). But if your system does not need this (now or in the future), Databasesystems like MySQL is excellent. WR "Kucera, Rich" wrote: > MySQL also contains some pretty practical advice regarding the > indiscriminate use of foriegn keys > (it even says they're only useful for visual design tools so designers can > more easily generate excess complexity > or something to that effect) >
- EJB w/ different DB's Frank Apap
- Re: EJB w/ different DB's Brien Voorhees
- Re: EJB w/ different DB's Elias Martensson
- Re: EJB w/ different DB's Jacob Smullyan
- RE: EJB w/ different DB's Neville Burnell
- RE: EJB w/ different DB's Kucera, Rich
- Re: EJB w/ different DB's Robert Kr�ger
- RE: EJB w/ different DB's Elias Martensson
- Re: EJB w/ different DB's Magnus Rydin
- Re: EJB w/ different DB's Elias Martensson
- RE: EJB w/ different DB's Jacob Smullyan
- RE: EJB w/ different DB's Kucera, Rich
- RE: EJB w/ different DB's Elias Martensson
- Re: EJB w/ different DB's Magnus Rydin
- Re: EJB w/ different DB's Elias Martensson
- Re: EJB w/ different DB's Magnus Rydin
- Re: EJB w/ different DB's Magnus Rydin
- Re: EJB w/ different DB's Robert Kr�ger
