Hi,

i was looking at the unsuported features in the RC4
docs and found this:

F671| Enhanced integrity management| Subqueries in
CHECK| intentionally omitted

Why is it *intentionally omitted*?
Is it to hard? or has some side-effects?

just a question!

regards,
Jaime Casanova

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

Search Discussions

  • Alvaro Herrera at Jan 9, 2005 at 4:15 pm
    On Fri, Jan 07, 2005 at 11:06:58PM -0600, Jaime Casanova wrote:

    Jaime,
    i was looking at the unsuported features in the RC4
    docs and found this:

    F671| Enhanced integrity management| Subqueries in CHECK| intentionally omitted

    Why is it *intentionally omitted*?
    Is it to hard? or has some side-effects?
    Because it's too expensive to check. If you have a CHECK using a SELECT
    against a second table, you should re-verify the SELECT every time the
    second table suffers an UPDATE, INSERT or DELETE.

    The user can replace the CHECK with a foreign key or a trigger, so there
    is no loss of functionality.

    --
    Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
    "No single strategy is always right (Unless the boss says so)"
    (Larry Wall)

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppgsql-hackers @
categoriespostgresql
postedJan 8, '05 at 5:07a
activeJan 9, '05 at 4:15p
posts2
users2
websitepostgresql.org...
irc#postgresql

2 users in discussion

Alvaro Herrera: 1 post Jaime Casanova: 1 post

People

Translate

site design / logo © 2021 Grokbase