Jean-Michel OLTRA wrote : > > bonjour, > > >I had problems with a dbproc using python (the insertion performed by >the dbproc skipped NEXTVAL). > >I dropped the table, and reloaded data. > >Then I tried to insert a record using my gui, and got an error : >"invalid date format : INTERNAL". The date field inserted is _not_ >invalid. > >I switched the instance in offline mode then in online mode >and retried. >Same error. > >I switched to offline, then online. Drop the dbproc and recreate it. >Then switched to offline, then online. And it works ! > >I previously had the same issue with my test instance, and had applied >the same protocol. > >When a table is dropped, its constraints are dropped with it. But not >the dbprocs using this table. > >When an object has been removed (and recreated) from an instance, is it >needed to recompile every dbproc using this object ? > > >-- >jm > > > >-- >MaxDB Discussion Mailing List >For list archives: http://lists.mysql.com/maxdb >To unsubscribe: >http://lists.mysql.com/maxdb?>[EMAIL PROTECTED] > >
Till now db-procedures have no knowledge about the objects accessed inside the dbproc and objects have no knowledge about the db-procedures using it. This means that today you have to recreate the db-procedures by hand whenever a change of an object accessed inside the procedure requires it. We will improve this behavior in the future, i.e. a db-procedure will be compiled automatically when necessary. Best Regards, Thomas -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
