Error Occurs on Large Updates
Posted: Mon 05 May 2008 21:59
Hi
As part of switchinmg to PostGres, we have to do reasonably large imports (consisting of arounf 400000 records) from various tables that come from a different database. All we do is get the data from the old database, loop through each record and update it to Postgres using ADO.NET, adapters, datatables and a command builder (we need to loop through because we often have to modify the data very slightly before it gets sent to PostGres). Whilst looping through the records we update them to the database about once every 1000 records. Very basic stuff, however the Corelabs provider will randomly error with "Error preprared statement PRSTMT2128149872399187 already exists" (or some equally large number). This happens at least once on virtually every import. Now I realize this is because CoreLabs must be generating a supposedly very large random number that is meant to be unique but computers don't seem to do random very well. So is there any way of stopping this from happening. If it only occured once every 100 imports, we wouldn;t jhave a problem, however I can state that it happens EVERY time at least once.
Any suggestions?
Thanks
Lee Ottaway
Fusion Software (UK) Ltd
As part of switchinmg to PostGres, we have to do reasonably large imports (consisting of arounf 400000 records) from various tables that come from a different database. All we do is get the data from the old database, loop through each record and update it to Postgres using ADO.NET, adapters, datatables and a command builder (we need to loop through because we often have to modify the data very slightly before it gets sent to PostGres). Whilst looping through the records we update them to the database about once every 1000 records. Very basic stuff, however the Corelabs provider will randomly error with "Error preprared statement PRSTMT2128149872399187 already exists" (or some equally large number). This happens at least once on virtually every import. Now I realize this is because CoreLabs must be generating a supposedly very large random number that is meant to be unique but computers don't seem to do random very well. So is there any way of stopping this from happening. If it only occured once every 100 imports, we wouldn;t jhave a problem, however I can state that it happens EVERY time at least once.
Any suggestions?
Thanks
Lee Ottaway
Fusion Software (UK) Ltd