Affects Version/s: 1.13.0
Fix Version/s: 1.13.0
In many places like this in Appointment Scheduling Module, we need to properly specify the sequences in hibernate mapping files. Properly map all the sequences to resolve this ticket.
Also there is a problem in actual length of sequence that can be stored in PostgreSQL. When length excedes the limit then table name gets stripped from end.
Here there is stripping in below sequences :
1. Original Sequence Name- appointmentscheduling_appointment_block_appointment_block_id_seq
Current name as set in AppointmentBlock.hbm file - appointmentscheduling_appointment_bloc_appointment_block_id_seq
2. Original Sequence Name- appointmentscheduling_appointment_request_appointment_request_id_seq
Current name as set in AppointmentRequest.hbm file - appointmentscheduling_appointment_re_appointment_request_id_seq
3. Original Sequence Name-appointmentscheduling_appointment_status_history_appointment_status_history_id_seq
Current name as set in AppointmentStatusHistory.hbm file - appointmentscheduling_appoint_appointment_status_history_id_seq
4. Original Sequence Name-appointmentscheduling_provider_schedule_provider_schedule_id_seq
Current name as set in ProviderSchedule.hbm file - appointmentscheduling_provider_schedul_provider_schedule_id_seq