Re: Another issue in default-values patch: defaults expanded too soon

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Another issue in default-values patch: defaults expanded too soon
Date: 2008-12-17 01:14:33
Message-ID: 49485279.302@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg,

> Well honestly I don't see a terribly compelling use case for default arguments
> altogether. Obviously they're just a programmer convenience and don't really
> let anyone do anything they couldn't do without them.

The primary use case is for people who are porting applications from
other DBMSes. Which don't support polymorphic arguments in the first place.

--Josh

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Brendan Jurd 2008-12-17 01:18:10 Re: Variadic parameters vs parameter defaults
Previous Message Gregory Stark 2008-12-17 01:11:24 Re: Another issue in default-values patch: defaults expanded too soon