The Logbook number & sequence are not unique always their is
duplication.
This duplication is solved by something they are using in
the billing system called subsequence.
Baha can explain this to you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mohammad?
Reading through the comments it looks like it's possible to
have a unique constraint over logbook number, sequence number
and subsequence number. Why is this not applied?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Baha: I think you did an analysis
that the combination of logbook numbers and sequence numbers
is NOT unique. Why don't you share this result with us here
so that it's properly documented?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=695149
The Logbook number & sequence are not unique always their is
duplication.
This duplication is solved by something they are using in
the billing system called subsequence.
Baha can explain this to you.
Logged In: YES
user_id=30248
This should be implemented as constraints on the database level.
Logged In: YES
user_id=695149
No comments on this issue. shall we keep it open. or shall
we close it.
Logged In: NO
Mohammad?
Reading through the comments it looks like it's possible to
have a unique constraint over logbook number, sequence number
and subsequence number. Why is this not applied?
Logged In: YES
user_id=30248
Baha: I think you did an analysis
that the combination of logbook numbers and sequence numbers
is NOT unique. Why don't you share this result with us here
so that it's properly documented?
Logged In: NO
there is a lot of duplication in this two fields
the logbook,sequence and subsequence must be unique
Logged In: YES
user_id=30248
Baha, please add a contstraint to create_dccss_ddl.sql.