OBYYS wrote:So your trigger is just a way of working around the app, from what I understand. Is it possible to adjust the app? Working around an application isn't a good reason to break normalization.
Thanks for your reply JUSTIN,
The point is that I'm working with another software which needs to automatically pull and deliver SMS messages to various members in the database. However, this software requires a particular table that will hold the phone number of receivers (i.e. Members in the database), and various unique messages that will be entered constantly in relation to each members ID_number, which needs to be delivered to each member via SMS.
This is what gave rise to my request for a proper Trigger syntax that would automatically update the column PHONE in Table B with data contained in the column PHONE in table A (with every entry made in Table B, where ID entered in B is thesame with I'd existing in A).
Thanks for your concern, i await your reply
OBYYS wrote:If the VIEW_NAME is the same as the TABLE_NAME; how will the application know the difference?
@sb92075 maybe you didnt get the part when i said that the SMS gateway software needs to periodically check for newly inserted rows in the table autmatically, which it will send out as message...... will creating a VIEW aid that function/task?