IRC log for #javaee, 2013-10-27

Please see http://irclog.greptilian.com/javaee for which days have been logged.

All times shown according to UTC.

Time	Nick	Message
00:59		SoniEx joined ##javaee
01:18		MegaMatt joined ##javaee
01:59		mbc joined ##javaee
06:55		cheater_3 joined ##javaee
07:44		acuzio joined ##javaee
08:30	acuzio	\q
11:43		acuzio joined ##javaee
11:44		acuzio left ##javaee
12:16		MegaMatt joined ##javaee
12:18		cheater_2 joined ##javaee
13:00		zoot joined ##javaee
13:04		acuzio joined ##javaee
13:10		ron joined ##javaee
13:10	ron	ah, he's not here.
13:10		ron left ##javaee
13:49		H4ml3t joined ##javaee
15:13		cheater_2 joined ##javaee
20:19		H4ml3t joined ##javaee
21:06		MegaMatt joined ##javaee
22:35		Quest joined ##javaee
22:35	Quest	I wonder how the JDBC or the Hibernate can let you know the id of a row that you just inserted in a database table? I know how its done but I really wonder how JDBC / hibernate gets the id of the newly made row. I never saw a native SQL for that. any ideas?
22:39	sfisque	depends on who's generating the id
22:39	Quest	sfisque, am. thats the normal way, when we stmt.execute i gues
22:40	Quest	pstmt
22:40	sfisque	if the db is generating it (via sequence or table lookup) then a followup query is performed. otherwise if jpa/hibernate is generating it, it has it "in hand"
22:40	Quest	oh. got your point. . I forgot to mention that the id in this case would be a pri_key auto generated.
23:47	Quest	sfisque, looks like the source of jdbc should be seen
23:48	sfisque	what does that sentence mean?

Please see http://irclog.greptilian.com/javaee for which days have been logged.