Statement#rows returning nil or 0?

Okay, how about:

1. http://rubyfo
rge.org/tracker/index.php? 
func=detail&aid=3176&group_id=234&atid=967 stays
on as a bug, albeit  
of a poorly written aspect of the DBD spec.

2. We rewrite that part of the DBD spec to say:

rows
   Returns the RPC (Row Processed Count) of the last
executed  
statement, or nil if the statement has not been executed.

I suppose we have to bump up the DBD spec version then, to
0.2.3.

Thoughts?

On Mar 29, 2006, at 3:02 PM, Paul DuBois wrote:

> On 3/28/06 13:28, "Francis Hwang"
<serafhwang.net> wrote:
>
>> Maybe it's clearer if I try to include the whole
context. The DBD
>> spec ( http://ru
by-dbi.rubyforge.org/DBD_SPEC.html ) says:
>>
>>    Methods that must be provided by Statement
>>    ...
>>    rows
>>        Returns the RPC (Row Processed Count) of the
last executed
>> statement, or nil if no such exists.
>>
>> But maybe the spec is actually unclear. Is it
saying Statement#rows
>> should return nil if there were 0 rows processed,
or that it should
>> return nil if there is no last executed statement?
The latter
>> actually makes a little more sense, though I don't
know if I've ever
>> done anything interesting with an un-executed
Statement.
>
> I interpret this to mean it returns 0 for 0 rows, and
nil (only) if  
> there is
> no last executed statement.
>
> In other words, nil is the exceptional condition.
>
>

Francis Hwang
http://fhwang.net/

_______________________________________________
Ruby-dbi-next mailing list
Ruby-dbi-nextrubyforge.org
h
ttp://rubyforge.org/mailman/listinfo/ruby-dbi-next

Statement#rows returning nil or 0?

Thread: Statement#rows returning nil or 0?