-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create additional unique constraints #59
Comments
A unique for the table courses on institution_id & course name is required for the search bar (#62) , since the lookup depends on this being unique. |
-removed content of this comment- reason: moved all conflicts to a list |
unique for the table courses on institution_id & course name implemented in local test database. 58 conflicts found. spreadsheet with proposed solutions is available. |
waiting for decisions in next meeting |
The spreadsheet with suggested solutions to fix the conflicts can be found here: |
Waiting for reaction on proposed solutions in spreadsheet. |
Update: In the spreadsheet linked above, I've marked the lines we can ignore in grey/black. As you can see in column G, only 21 courses are left, that's were we need to take a decision about. Can you tell if the proposed changes in column H can be made? |
Hi Patrick while checking the courses it came to my mind, that this might happen again in the future: Hence, the following idea came to my mind: very much looking forward to the deployment of the new feature! |
@PixlTracer Thanks for taking a look at the list. I'd like to divide you comment in thee parts.
In the future we don't have to do that. That is what the implementation of the combination of Course Name + Institution + Education Type being unique means. As soon as this is in production, the application will do that for us.
Can we continue the talk about the search bar in the corresponding issue? Here:
Thanks for your suggestions, I have a few remarks.
Link to the spreadsheet (again): https://docs.google.com/spreadsheets/d/1V6rUDUKE34EhwGgMYg0dylOUwJB0nlLP6wlSnKgeeZY/edit?usp=sharing Based on your suggestions, I've made a new proposal in column J. Can it be changed like that? |
As discussed in the meeting today, the proposal in column J is agreed and the changes can be made. |
thank you! |
Great that you're happy with the implemented solution. This was only one validation rule. (Which was prioritized, because it was needed earlier) I'll move the issue to a next milestone and then the following validation rules can be implemented;
|
No time available for this now, moved to November milestone. It's still important because it contributes to the quality of the data. |
|
currently it's possible to enter duplicate data in the admin area. the following items should be unique: cities, countries, courses: on institution_id & course name, faq_questions.name, invite_translations.language_id, languages
create these rules in the database and application.
fix conflicts when they occur.
The text was updated successfully, but these errors were encountered: