On Mon, Jan 26, 2009 at 2:53 PM, Phoenix Kiula wrote:
> On Mon, Jan 26, 2009 at 9:45 PM, Matthias Karlsson wrote:
>> On Mon, Jan 26, 2009 at 2:09 PM, Phoenix Kiula
>> wrote:
>>> I wonder if this is an SQL limitation or something I'm missing in the
>>> PG
On Mon, Jan 26, 2009 at 2:09 PM, Phoenix Kiula wrote:
> I wonder if this is an SQL limitation or something I'm missing in the
> PG manual, but I need to run an update on my database (to replace the
> value of a column to match a new design structure).
>
> Due to the new business logic, the replac
DbVisualizer is a tool I have used in the past for exactly this.
// Matthias
On Wed, Nov 5, 2008 at 1:18 PM, Mohammad Ali Darvish Darab
<[EMAIL PROTECTED]> wrote:
> Hello everybody,
>
> I have got an already existing Porstgres DB which is pretty large
> (including more than 650 table with consid
Why do you need to store the total area at all (property_area)? This
value can easily be calculated with an group by query.
On Mon, Oct 20, 2008 at 10:56 PM, Karl Nack <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I'm a bit of a newb designing a database to hold landcover information for
> propertie
Tom Lane skrev:
"Matthias Karlsson" <[EMAIL PROTECTED]> writes:
I have a rather complex set of relations, connected with cascading
foreign keys on delete. I'm experiencing very slow performance when
deleting *the* lead node, which everything eventually depends on.
Hi,
I have a rather complex set of relations, connected with cascading
foreign keys on delete. I'm experiencing very slow performance when
deleting *the* lead node, which everything eventually depends on. The
number of records ultimately to be deleted aren't that many (perhaps
2000-3000) but there
