On Wednesday 17 May 2006 18:12, Jim C. Nasby wrote:
> In any case, there's extensive discussion about this in the -hackers
> archives. IIRC, there is consensus that this would be nice to have but
> no one has cared enough to actually make it happen. There are some
> non-trivial issues since this wo
Emi Lu wrote:
No. It is not for select.
I have tens of tables with very clean structure. For example, username,
application_code, last_modified_by, etc in specific orders.
Since the business model is changed, I have to add some columns to
serveral tables.
I prefer columns orders followin
Jim C. Nasby wrote:
On Wed, May 17, 2006 at 05:48:52PM -0400, Emi Lu wrote:
I think it is a very useful feature for postgresql to support it.
If we have this feature supported, I do not have to recreate the table
and resetup all foreign key constraints, views, triggers, etc that are
based
On Wed, May 17, 2006 at 05:48:52PM -0400, Emi Lu wrote:
> I think it is a very useful feature for postgresql to support it.
>
> If we have this feature supported, I do not have to recreate the table
> and resetup all foreign key constraints, views, triggers, etc that are
> based on the table.
U
This feature seems by a mysql add tu create table command, only mysql can do
dat.
Alejandro Michelin Salomon
I think it is a very useful feature for postgresql to support it.
If we have this feature supported, I do not have to recreate the table
and resetup all foreign key constraints,
Hi Ying:
This feature seems by a mysql add tu create table command, only mysql can do
dat.
Alejandro Michelin Salomon
-->-Mensagem original-
-->De: [EMAIL PROTECTED]
-->[mailto:[EMAIL PROTECTED] Em nome de Emi Lu
-->Enviada em: quarta-feira, 17 de maio de 2006 18:21
-->Para: pgsql-gen
