Thread:

From
suri
Date:
I have created a function to update the data in the table in postgres and i
have 33k records to update. When i was calling the function as SQL the data
is updated fine. But when i was calling the same function through callable
statement only about 28k records are updated in the table and it was
skipping the remaining records no exceptions have thrown. please help me on
this issue.

this is my code. CallableStatement callStatement =3D
ConnectionDB.getConnectionInstance().prepareCall(" { ? =3D call
functionname()}"); callStatement.registerOutParameter(1, Types.VARCHAR);
callStatement.execute();



/*- =96 - =96 - =96 =96 - =96 =96 - =96 =96 - =96 =96 - =96 =96 - =96 =96 -=
 =96 =96 - =96 =96 - =96 =96 - =96 =96 - -

Please consider your environmental responsibility.
Before printing this e-mail message, ask yourself whether you really need a
hard copy.

Life is what happens to you, while you're busy making other plans

We do not inherit the earth from our ancestors; we borrow it from our
children.
Leave them a living planet reduce your carbon foot print.
------------------------------------------------------------
--------------------------------*/






yours suri chinna

Re:

From
John R Pierce
Date:
On 11/5/2013 11:22 PM, suri wrote:
>
> I have created a function to update the data in the table in postgres
> and i have 33k records to update. When i was calling the function as
> SQL the data is updated fine. But when i was calling the same function
> through callable statement only about 28k records are updated in the
> table and it was skipping the remaining records no exceptions have
> thrown. please help me on this issue.
>
> this is my code. CallableStatement callStatement =
> ConnectionDB.getConnectionInstance().prepareCall(" { ? = call
> functionname()}"); callStatement.registerOutParameter(1,
> Types.VARCHAR); callStatement.execute();
>

PostgreSQL has no 'call' statement, you use SELECT to call a function.
    Is that code fragment Java or what?

there is insufficient information here to determine if this is in fact
some sort of bug, or rather a user misunderstanding, or what.




--
john r pierce                                      37N 122W
somewhere on the middle of the left coast