It also depends on how many records and indexes the table has. With too many records an update of a column that doesn't belong to an index could be faster than an insert which has to update all the indexes.
2009/11/25 Andrej Hopko <ado.ho...@gmail.com> > Hi, > my standard knowledge is that inserts are cheap for database to > run, but deleting and updating are expensive operations (if this you > meant by fat operation) > > difference is mainly due to usage of indexes and locks (thats my > opinion) > > hoppo > > On 25.11.2009 23:16, noam gariani wrote: > > Do you know what is fater? > > To do update for a record , or insert a record to a db? > > > > > > -- > You received this message because you are subscribed to the Google > Groups "Oracle PL/SQL" group. > To post to this group, send email to Oracle-PLSQL@googlegroups.com > To unsubscribe from this group, send email to > oracle-plsql-unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/Oracle-PLSQL?hl=en > -- You received this message because you are subscribed to the Google Groups "Oracle PL/SQL" group. To post to this group, send email to Oracle-PLSQL@googlegroups.com To unsubscribe from this group, send email to oracle-plsql-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Oracle-PLSQL?hl=en
