backend vs frontend bookings
I am building a booking/appointments app...
In it...there are two types of appointments...the ones the get closed from the web user(in the frontend side) and the ones that get closed from the business user in the backend.
One characteristic that separates the two is that the fronted appointments must be verified through mail before stored permanently in the database.
That calls for a column value of true/false depending if the appointments has been verified or not...
And here is the problem...both types of appointments are stored in the same table.
Regarding the backend appointments...what value must I give to that row/column.
Backend appointments require no verification.
I have concluded that this column must be default NULL...to cover the case of the backend appointments...
What do you think about that?
Subject
Written By
Posted
backend vs frontend bookings
January 25, 2016 05:06AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.