Re: select issue with order v8.1

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Terry <td3201(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: select issue with order v8.1
Date: 2010-02-26 22:52:39
Message-ID: dcc563d11002261452u63a369b6p1cac23c3be103c46@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Feb 26, 2010 at 3:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Terry <td3201(at)gmail(dot)com> writes:
>> I am somewhat confused.  My app is detecting it as a serial data type
>> but describing the table shows that its an integer.  What am I
>> missing?
>
>> dssystem=# \d clients_event_log
>>                                        Table "public.clients_event_log"
>>      Column     |          Type           |
>>  Modifiers
>> ----------------+-------------------------+-------------------------------------------------------------------
>>  ev_id          | integer                 | not null default
>> nextval('clients_event_log_ev_id_seq'::regclass)
>
> Nothing.  "Serial" is nothing but a shorthand for an integer column
> with a default like that.

And a dependency for the sequence on the column. I wonder if Terry's
application is sorting through dep info to make a bad decision...

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Hiroshi Inoue 2010-02-26 23:06:31 Re: trouble with to_char('L')
Previous Message Tom Lane 2010-02-26 22:46:00 Re: select issue with order v8.1