ORM: when to raise an exception: on object creation or on use?

Path	csiph.com!news.swapon.de!aioe.org!.POSTED!not-for-mail
From	Victor Porton <porton@narod.ru>
Newsgroups	comp.databases.object, comp.programming
Subject	ORM: when to raise an exception: on object creation or on use?
Followup-To	comp.programming
Date	Fri, 04 Sep 2015 17:15:53 +0300
Organization	Aioe.org NNTP Server
Lines	7
Message-ID	<msc92o$peq$1@speranza.aioe.org> (permalink)
NNTP-Posting-Host	789z/vFFztmOQ/etbIfqnA.user.speranza.aioe.org
Mime-Version	1.0
Content-Type	text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding	7Bit
X-Complaints-To	abuse@aioe.org
User-Agent	KNode/4.14.1
X-Notice	Filtered by postfilter v. 0.8.2
Xref	csiph.com comp.databases.object:60 comp.programming:5799

Cross-posted to 2 groups.

Followups directed to: comp.programming

Show key headers only | View raw

Should an ORM implementation query the DB as soon as an active record is 
created in order to check that the queried row exists in DB, or is it OK to 
throw an exception later when attempting to access a field (for an 
nonexistent row)?

-- 
Victor Porton - http://portonvictor.org

Back to comp.databases.object | Previous | Next | Find similar

Thread

ORM: when to raise an exception: on object creation or on use? Victor Porton <porton@narod.ru> - 2015-09-04 17:15 +0300

csiph-web