No way you can make sure at application level. Think in sense of an uncommitted 
row and other session inserting at the same moment in time.


Thanks,
Atul Goel


-----Original Message-----
From: Gnanakumar [mailto:gna...@zoniac.com]
Sent: 18 January 2012 12:59
To: Atul Goel; pgsql-general@postgresql.org
Subject: RE: [GENERAL] On duplicate ignore

> Just create a unique index on EMAIL column and handle error if it
> comes

Thanks for your suggestion.  Of course, I do understand that this could be 
enforced/imposed at the database-level at any time.  But I'm trying to find out 
whether this could be solved at the application layer itself.  Any 
thoughts/ideas?



The information contained in this email is strictly confidential and for the 
use of the addressee only, unless otherwise indicated. If you are not the 
intended recipient, please do not read, copy, use or disclose to others this 
message or any attachment. Please also notify the sender by replying to this 
email or by telephone (+44 (0)20 7896 0011) and then delete the email and any 
copies of it. Opinions, conclusions (etc) that do not relate to the official 
business of this company shall be understood as neither given nor endorsed by 
it. IG Group Holdings plc is a company registered in England and Wales under 
number 04677092. VAT registration number 761 2978 07. Registered Office: Cannon 
Bridge House, 25 Dowgate Hill, London EC4R 2YA. Listed on the London Stock 
Exchange. Its subsidiaries IG Markets Limited and IG Index Limited are 
authorised and regulated by the Financial Services Authority (IG Markets 
Limited FSA registration number 195355 and IG Index Limited FSA registration 
number 114059).

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Reply via email to