P=C3=A5 tirsdag 05. februar 2013 kl. 13:32:15, skrev Alban Hertroys &l=
t;haramrae@gmail.co=
m>:
<blockquote style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt=
0pt 0pt 0.8ex; padding-left: 1ex;">On 5 February 2013 12:41, Andreas Josep=
h Krogh <<a href=3D"mailto:andreak@officenet.no" targe=
t=3D"_blank">andreak@officenet.no> wrote:
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
There are lots of things you can do, but when it's the ORM which does =
it you have limited control, and that's the way it should to be (me as appl=
ication-developer having to worry less about such details).
=C2=A0
In that case it's your ORM that needs fixing, not the database.
=C2=A0
"Fix your tool" is not helping here... Having deferrable NOT=
NULLs in the RDBMS will help making peoples lives easier and (some) other =
RDBMS have this.
=C2=A0
My question was if having deferrable NOT NULLs was on PGs road-map, no=
t whether or not someone finds it usefull or is able to work around it.</di=
v>
=C2=A0
--
Andreas Joseph Krogh <andreak@officenet.no>=C2=A0 =C2=A0 =C2=A0 mob: =
+47 909 56 963
Senior Software Developer / CTO - OfficeNet AS - http://www.officenet.no
Public key: http://home.officenet.no/~andreak/public_key.asc
=C2=A0=
