Georg Thome wrote: > > If I understand you right, you want to preserve the data of one row > being changed after insertion. > I think the only way for doing this is via triggers. > You have to implement a BEFORE UPDATE and a BEFORE DELETE trigger on > that table.
Nice idea, but MaxDB does not support BEFORE-trigger. Therefore the normal triggers (triggered after each row) have to be used and the OLD-values (Update) resp. the row-values (delete) checked, causing the trigger to fail --> update/delete to fail. Elke SAP Labs Berlin > Georg > Nick Chan wrote: > > hi > > > > is there a way to make data in a field read-only after > first time being added/set ? > > > > thanks > > > > > -- > Georg Thom� IEE Luxembourg S.A. > IT dept. / software development / DB-administation > tel. 00352/7289896810 fax 00352/7289896109 > www.iee.lu / [EMAIL PROTECTED] > > This e-mail may contain trade secrets or privileged, undisclosed or > otherwise confidential information. If you are not the > intended recipient > and have received this e-mail in error, you are hereby > notified that any > review, copying or distribution of it is strictly prohibited. Please > inform us immediately and destroy the original transmittal from your > system. Thank you for your co-operation. > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
