> > > Can someone tell me what an appropriate use for REPLACE is? > > Replace might be used if you had a user_permission_info table, and were editing things about the user like maybe lastname/staffID ... password... but then with replace you MUST reference all unique keys...but basicallly the user is still the same user; not a new guitar
If you have constraints between your tables (like cascade on delete) then deleting a guitar entry would remove its related entirs in other tables referencing that same ID. But ya I agree, generally it is a more robust solution to use if 'update' fails, then insert; -Bill > CONFIDENTIALITY, EXPORT CONTROL AND DISCLAIMER NOTE:This e-mail and any > attachments are solely for the use of the addressee and may contain > information that is privileged or confidential. Any disclosure, use or > distribution of the information contained herein is prohibited. In the > event this e-mail contains technical data within the definition of the > International Traffic in Arms Regulations or Export Administration > Regulations, it is subject to the export control laws of the > U.S.Government. The recipient should check this e-mail and any attachments > for the presence of viruses as L-3 does not accept any liability associated > with the transmission of this e-mail. If you have received this > communication in error, please notify the sender by reply e-mail and > immediately delete this message and any attachments. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
