StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17232696
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-21T10:12:12.477
FavoriteCount
0
LastActivityDate
2013-06-21T13:23:56.457
LastEditDate
2017-05-23T12:29:37.523
LastEditorUserId
-1
OwnerUserId
1523390
ParentId
17196790
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I've made the following (rough) tests just to illustrate the cost of raising an exception vs checking if columns exist in the RecordSet, in my particular case. The number of columns to check was 169. Code 1 <pre><code>try { sTemp = this.rsResults.getString("col3"); }catch(Exception e){} try { sTemp = this.rsResults.getString("col4"); }catch(Exception e){} ... try { sTemp = this.rsResults.getString("col169"); }catch(Exception e){} </code></pre> Code 2 with function hasColumn [question]:<a href="https://stackoverflow.com/questions/3599861/how-can-i-determine-if-the-column-name-exist-in-the-resultset">How can I determine if the column name exist in the ResultSet?</a> <pre><code>ResultSetMetaData rsmd = null; try { rsmd = this.rsResults.getMetaData(); } catch (SQLException e1) { e1.printStackTrace(); } try{ if (rsmd != null && hasColumn(rsmd,"col3")) sTemp = this.rsResults.getString("col3"); }catch(Exception e){} try{ if (rsmd != null && hasColumn(rsmd,"col4")) sTemp = this.rsResults.getString("col4"); }catch(Exception e){} ... try{ if (rsmd != null && hasColumn(rsmd,"col169")) sTemp = this.rsResults.getString("col169"); }catch(Exception e){} </code></pre> Results without c3p0 <pre><code> code 1 code 2 query nº1 75ms 36ms query nº2 40ms 43ms query nº3 227ms 46ms query nº4 262ms 18ms </code></pre> Results with c3p0 loglevel at INFO <pre><code> code 1 code 2 query nº1 519ms 45ms query nº2 358ms 28ms query nº3 2348ms 9ms query nº4 3243ms 12ms </code></pre> As a conclusion the cost of raising an exception just to check if columns exists (besides of being bad practice) is high in both cases and especially if using c3p0.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POResultSet "column not found" with c3p0
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USAndreFonseca
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.