Thread: Re: [GENERAL] Resultset problem or BUG !

Elie Nacache wrote:

>     this.sqlDatas.moveToInsertRow();
>     this.updateColumns();
>     this.sqlDatas.insertRow();

The JDBC javadoc implies that calling insertRow() leaves the resultset
on the insert row. This is what the driver implements.

>     this.sqlLineNumber = this.sqlDatas.getRow(); // INFO >> return 0

As the javadoc says, getRow() returns 0 if there is no current row.
You're on the insert row so there is no current row.

>     INFO >> At this step there is no commit
>     INFO >> Second step update the row after collecting updated info
>
>     this.sqlDatas.absolute(this.sqlLineNumber); // INFO >> throw the
>     exception

What is the exception you see?

The current development driver (see jdbc.postgresql.org) will treat
absolute(0) as if you'd called beforeFirst(). Older drivers might do
something different.

>     this.updateColumns();
>     this.sqlDatas.updateRow();
>     INFO >> If I fix the sqlLineNumber to 1 and force the absolute(1)
>     then no Execption is thrown but the modification is not seen in the
>     table.

Looking at the driver source, it looks like the newly inserted row is
appended to the resultset, so you should find it at the end of the
resultset not the start. (I don't think making this assumption is
portable, though).

-O

On Wed, 11 Aug 2004, Elie Nacache wrote:

> INFO >> sqlDatas is of type ResultSet
> INFO >> Step first insert new row
>
> this.sqlDatas.moveToInsertRow();
> this.updateColumns();
> this.sqlDatas.insertRow();
> this.sqlLineNumber = this.sqlDatas.getRow(); // INFO >> return 0
>

The problem here is that you are still on the insert row, you are not
positioned anywhere in your ResultSet so getRow returns zero.  You seem to
be expecting getRow to return the newly inserted row's position which I
admit seems handly although it doesn't look to be what the spec wants.

Kris Jurka

Elie Nacache wrote:

> this.sqlDatas.moveToInsertRow();
> this.updateColumns();
> this.sqlDatas.insertRow();

The JDBC javadoc implies that calling insertRow() leaves the resultset
on the insert row. This is what the driver implements.

> this.sqlLineNumber = this.sqlDatas.getRow(); // INFO >> return 0

As the javadoc says, getRow() returns 0 if there is no current row.
You're on the insert row so there is no current row.

> INFO >> At this step there is no commit
> INFO >> Second step update the row after collecting updated info
>
> this.sqlDatas.absolute(this.sqlLineNumber); // INFO >> throw the
> exception

What is the exception you see?

The current development driver (see jdbc.postgresql.org) will treat
absolute(0) as if you'd called beforeFirst(). O lder drivers might do
something different.

> this.updateColumns();
> this.sqlDatas.updateRow();
> INFO >> If I fix the sqlLineNumber to 1 and force the absolute(1)
> then no Execption is thrown but the modification is not seen in the
> table.

Looking at the driver source, it looks like the newly inserted row is
appended to the resultset, so you should find it at the end of the
resultset not the start. (I don't think making this assumption is
portable, though).

-O

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

On Sun, 15 Aug 2004, Elie Nacache wrote:

> > The current development driver (see jdbc.postgresql.org) will treat
> > absolute(0) as if you'd called beforeFirst(). Older drivers might do
> > something different.
>
>  This is exactly the solution.

No, I don't believe it is.  If it was you could just change your code to
call beforeFirst() instead because getRow() will always return zero when
it is on the insert row.  This is your real problem.  You are expecting
getRow() to return the value of the newly inserted row which it does not.

Kris Jurka