From: Kevin M. <mu...@ge...> - 2004-12-07 19:55:28
|
Angel Pizarro wrote: > The GUS XML parser is not a real XML parser. The order of the columns > matter. Put <PROTOCOL_ID> before <PROTOCOL_TYPE_ID> Grrr, but thanks. Now I have a problem where the number of columns in RAD3Ver.ProtocolVer (24) is apparently not large enough (number of rows in RAD3.Protocol is 23). Hmm. Here is the error: sqlExec: INSERT INTO RAD3Ver.ProtocolVer select v.*,312,SYSDATE,11 from RAD3.Protocol v where v.protocol_id = ? bindValues (1) DBD::Oracle::st execute failed: ORA-00913: too many values (DBD ERROR: error possibly near <*> indicator at char 20 in 'INSERT INTO RAD3Ver.<*>ProtocolVer select v.*,312,\ SYSDATE,11 from RAD3.Protocol v where v.protocol_id = :p1') [for Statement "INSERT INTO RAD3Ver.ProtocolVer select v.*,312,SYSDATE,11 from RAD3.Protocol v where v.protoco\ l_id = ?" with ParamValues: :p1='1'] at /checkout/GUS/lib/perl/GUS/ObjRelP/DbiDbHandle.pm line 146, <GEN0> line 12. There's nothing in RAD3Ver.ProtocolVer right now, BTW. If I don't have the right definition for it for some reason, it would be straightforward to recreate it. Kevin Murphy |