From: Fidel S. <fi...@vb...> - 2004-01-16 12:40:07
|
Steve, The SubmitRow algo_invo option does not seem to work, or at least does not work as I would expect it to. Needing to upload some type of data that GUS does not currently address, I needed to use SubmitRow for inserting 10s of thousands of rows into a view. I thought that if I used the algo_invo option I could use the same algorithm_invocation_id for all inserts. Therefore, I wrote a script that would do the initial insertion, get that initial insertion's algorithm invocation id, and then invoke SubmitRow with the algo_invo option (with the value being the initial algorithm invocation id). SubmitRow then proceeds to do the insertions but ignores the algo_invo option and creates algorithm invocation ids for all the new inserts. Is my interpretation of how the algo_invo option should work not correct? Or is that option only to be used when the system can absolutely not generate new ids? If the latter, it seems to me that if the system cannot generate new ids, one should not be inserting new data and fix the problem of not being able to generate new ids. Thanks Fidel > Message: 3 > Date: Thu, 15 Jan 2004 19:45:02 -0500 > From: Steve Fischer <sfi...@pc...> > To: gusdev-gusdev <gus...@li...> > Subject: [Gusdev-gusdev] SubmitRow fixed > > Folks- > > I have fixed up GUS::Common::Plugin::SubmitRow. It now works on > updates. Also, the code is cleaner, so it is a good sample plugin. > > Steve |