1 Reply Latest reply on Aug 25, 2001 12:58 AM by David Jencks

    Creating new bean - BeanExistsCommand problem

    Paul Jones Newbie

      I've noticed that before creating a bean which maps to a db table a check is made to see that the new bean does not exist in the database (Oracle 8) prior to insert - why does it does this when Oracle checks anyway? Is there a way of turning this off? I've had a look at the source and it doesn't look like you can.

        • 1. Re: Creating new bean - BeanExistsCommand problem
          David Jencks Master

          Well, Oracle and most other "relational" databases only check primary keys and unique indexes for uniqueness problems. There is no requirement that your tables have any such constraints, nor is there a requirement that e.g. the pk be part of the bean. Obviously any such design is questionable at best, however better safe than sorry. It might well be a good idea to be able to turn the checking off.