Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

Limitations in m-to-m rel & check duplicates? 27 Jul 2012 08:53 #2913

  • tr4ding
  • tr4ding's Avatar Topic Author
  • Offline
  • Senior Member
  • Senior Member
  • Posts: 42
  • Thank you received: 0
HI Folks :)

My component is structured in a lot of many to many relations.......

I think in JCook there are 2 main problems:

1. I am forced to use a surrogate primary key in a many to many relation table....

eg. (correct according to DBMS literature)

table: student_exams
Fields:
id_student
id_exam
other fields..........

same eg. (when I use JCook framework)

table: student_exams
Fields:
id
id_student
id_exam
other fields.........

2. In JCook, I'm unable to check duplicates in tables......this can cause Database inconsistency.....expecially in a many-to many-relation table.....

Proposed solution

Problem n.1 is marginal in JCook roadmap........

My idea is to use InnoDB Engine instead of MyISAM in order to impose referential constraints in tables.......could this work to prevent problem n. 2?

I think (but I prefer to be contradicted :) ) that cascade function to delete FK doesn't work properly or I don't understand how it works properly for my case study.....

Have a nice day :)

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.065 seconds

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started