Added to TODO:
* Add TRUNCATE ... CASCADE
---------------------------------------------------------------------------
Josh Berkus wrote:
> Guys,
>
> > I wouldn't care for that either. The prior suggestion of "TRUNCATE tab
> > CASCADE" (to truncate any tables with FK dependencies on the original
> > target, instead of failing) seems more reasonable.
>
> I agree with Tom ... even the idea of a "TRUNCATE ALL" makes me nervous. If
> we had such a feature, I'd advocate that it be superuser only.
>
> As for "TRUNCATE CASCADE" or similar improvements, I agree that they could be
> convenient ... but are easily worked around currently. So I wouldn't object
> to putting TRUNCATE CASCADE on the todo list, but would argue that it be left
> to the people who asked for it to implement it.
>
> As far as
>
> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
