On Wed, 16 Oct 2002, Tom Lane wrote:
> =?ISO-8859-1?Q?Crist=F3v=E3o_Dalla_Costa?= <[EMAIL PROTECTED]> writes:
> > In PostgreSQL 7.3b2, if I create a table like so:
> > create table customers (id serial primary key);
>
> > The id field will be created of type 32 bit integer, yet the upper limit
=?ISO-8859-1?Q?Crist=F3v=E3o_Dalla_Costa?= <[EMAIL PROTECTED]> writes:
> In PostgreSQL 7.3b2, if I create a table like so:
> create table customers (id serial primary key);
> The id field will be created of type 32 bit integer, yet the upper limit
> for the sequence will be relative to a 64 bit i
> > May I ask why you don't want to go with something like:
> > #define DESCR(x) typedef int postgresql_foo_bar
>
> Because it doesn't work.
> $ cat z.c
> typedef int postgresql_foo_bar;
> typedef int postgresql_foo_bar;
> $ gcc -c z.c
> z.c:2: redefinition of `postgresql_foo_bar'
> z.c:1: `postgr
In PostgreSQL 7.3b2, if I create a table like so:
create table customers (id serial primary key);
The id field will be created of type 32 bit integer, yet the upper limit
for the sequence will be relative to a 64 bit integer.
\d customers
Table "public.customer
Dan Wilder ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
Data in table causes server to terminate with signal 11
Long Description
I have a table which brings about the error message (from syslog)
server process (pid 21503)
"ir. F.T.M. van Vugt bc." <[EMAIL PROTECTED]> writes:
> May I ask why you don't want to go with something like:
> #define DESCR(x) typedef int postgresql_foo_bar
Because it doesn't work.
$ cat z.c
typedef int postgresql_foo_bar;
typedef int postgresql_foo_bar;
typedef int postgresql_foo_bar;
$
Tom Lane writes:
> That's hard to believe; I think it's Qt that's doing something strange
> here.
As a newbie on the list, I'm sorry I have to disagree with you, Tom... ;)
The fact that PostgreSQL dissolves stuff into something like:
#include
extern int errno;
extern int errno;
was more of a
