| |
| |
| |
|
Page: 1 2
Comments:
<0> It would probably be more effecient to do a count query though - that would prevent the database layer from having to retrieve the values at each row iteration.
<0> Hmm.. actually that may be deferred until you actually request the value. That's probably implementation specific, don't quote me on it. :P
<1> Emule: what for do you need to know the number of rows in the resultset?
<2> yes
<2> :)
<1> Emule: who are you talking to?
<0> Clackwell: would you happen to know if the retrieval of those values is deferred or not? I'm just curious... I'd imagine it's implementation specific since ResultSet does nothing more than define an interface.
<1> Resonator: yeah, must be implementation specific i'd say too.
<0> OK, cool.
<2> if number = 0 then row not exist
<1> Emule: who are you talking to?
<1> Emule: what for do you need to know the number of rows in the resultset?
<3> resultset? You don't need to implement it.
<0> Lion-O: no, the DB driver vendor does though. :)
<3> aah, ok.
<1> hi lion. the question was wether some behavior may be implementation specific. since the jdbc api is just an interface, it has to be, i guess.
<3> Resonator: then I misread ;-)
<3> Clackwell: ey there
<1> Emule: what for do you need to know the number of rows in the resultset?
<2> boolean Exist (String PKey)
<2> {
<2> if(resultset."number of rows"== 0)
<2> return false;
<2> else
<2> return true;
<2> }
<0> The hell
<1> ...and for flooding the channel with stuff that should go to internet pastebins...
<3> I think someone is trolling.
<2> Clackwell ??
<0> Is that supposed to be pseudo code or something?
<1> Emule: use ResultSet.next() - see api docs for what it returns.
<1> Emule: the COUNT route that Resonator suggested works too.
<1> for that case
<2> ok
<4> in fact, the count method ought to be orders of magnitudes faster than itterating a sizeable resultset
<5> thks friends
<5> salam
<4> it's tempting to treat the database resultset as you would an in-memory collection, but they are two very very diffrent beasts
<1> wlfshmn: unless you pull the stuff into memory. in case of our db engine you can tell it to do so in a per query basis or in general.
<1> i seem to recall something like that for ms sql server too.
<1> scrollable resultsets are related, too.
<1> and that cached/disconnected rowset thingy
<6> can anybody pls give me a link where i can download the plugin for "grphic interface maker" for eclipse?
<1> Mathusalem: never heard of that.
<1> one hit at google for "graphic interface maker". you definitely got the wrong keyword there.
<1> if you are looking for java gui builders, search for those.
<7> jigloo
<7> its a plugin for eclipse
<7> it's cool
<4> Clackwell: Well, ofcourse. But typically you don't want to cache the entire dataset, and when you do, they are rather small sets
<4> Clackwell: If I wanted to cache the data, I expect hibernate can do that for me in most cases
<1> yeah
<1> people who pull everything in in non trivial systems are poor programmers, maybe. either because they are naive about resource usage or db phobic or db ignorant.
<1> that said, i love rdbms centrism. :)
Return to
#java
or
Go to some related
logs:
Iceni Queen battled the Romans
Who was the American psychologist known for his experiments with hallucinogenic
vecotr unresolved
how to disable dhcp on netgear rp614 to make normal router
#php
#linux
#MissKitten
#linux
#AllNiteCafe
#c++
|
|