supposed to be. I would like to have a more
self-explanatory solution like 1 or 2.
I wonder if there is something better.
Best regards, Matthias
--
Matthias Nagel
Willy-Andreas-Allee 1, Zimmer 506
76131 Karlsruhe
Telefon: +49
ql.org/message-id/4f8bb9b0.5090...@darrenduncan.net . Does
anybody know about the progress?
Having range types and exclusion contraints are nice, as I said in the
introdruction. But if the reverse (foreign key with inclusion) would also work,
the range type feature would really be amazing.
WHERE ..." part, because the tempory calculation needs some
input values from the same table. Hence the table is looked up twice instead
once.
Matthias
Am Samstag 29 September 2012, 17:13:18 schrieb Andreas Kretschmer:
>
> Thomas Kellerer hat am 29. September 2012 um 16:13
> ge
Hello,
> Matthias Nagel hat am 29. September 2012 um 12:49
> geschrieben:
> > Hello,
> >
> > is there any way how one can store the result of a time-consuming
> > calculation
> > if this result is needed more than once in an SQL update query? This
> >
duration time. First of all it would make the SQL statement faster and secondly
much more cleaner and easily to understand.
Best regards, Matthias
------
Matthias Nagel
Willy-Andreas-Allee 1, Zimmer 506
76131 Karlsruhe
Telefon