Hi Dave,
I had a look at triggers and views where functions are referenced using OIDs.
Cheers/ JMP
>Good night,
Good night!
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 02 October 2001 21:30
> To: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Table modification
>
>
>
> >OK, following some tests I find that PostgreSQL doesn't validate a
> >PL/pgSQL function when i
>OK, following some tests I find that PostgreSQL doesn't validate a PL/pgSQL
>function when it builds it as I thought. I tend to use plain SQL functions
>which are validated so the situation you describe above cannot occur. That
>is why I figure that the best validation is to actually build each
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 02 October 2001 18:38
> To: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Table modification
>
>
>
> >Yes. So you use Revision Controls Rollback option (planned,
> but not yet
> >implemented) to u
>Yes. So you use Revision Controls Rollback option (planned, but not yet
>implemented) to undelete the object if it wasn't supposed to be dropped,
>otherwise it doesn't matter because you obviously don't want to publish it
>anyway.
No, source code should never be 'rolled back'.
We have to distin
>This should be fixed now. Char columns get converted to bpchar in
>PostgreSQL, but you can't specify a length for bpchar!
>
>All columns will now display correctly as char(n).
>
>Regards, Dave.
Hello my friend,
The only thing we can trust is plain 'source code' not PostgreSQL derived
or user
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 02 October 2001 16:34
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-hackers] Column lenght
>
>
> Hello,
>
> Try the following query:
> create table essai(
> ID char(12) not null,
> primary key
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 02 October 2001 15:51
> To: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Table modification
>
>
>
> >1) I don't want to retrieve source from logs. I want to analyse the
> >database and generate t
Hello,
Try the following query:
create table essai(
ID char(12) not null,
primary key (id)
);
The definition pane displays no lenght:
CREATE TABLE "essai" (
"id" bpchar NOT NULL,
CONSTRAINT "essai_pkey" PRIMARY KEY ("id")
);
The property editor show the correct column l
>1) I don't want to retrieve source from logs. I want to analyse the database
>and generate the source from what is known to work and compile correctly.
>There is no better test for an object than to build it in PostgreSQL.
When an object is broken, its source code disappears or cannot be retrie
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 02 October 2001 14:47
> To: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Table modification
>
> >Another idea to consider: The Publishing Wizard. I believe this
> >provides roughly the same faciliti
>pgAdmin I *will not* work with PostgreSQL 7.2. Bear that in mind if you look
>to upgrade.
I will not upgrade to PostgreSQL 7.2 before pgAdmin I development features
are ported, one way or another, to pgAdmin II.
>Where else would the input come from if not the user?
>
>The logs are more relia
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 02 October 2001 13:26
> To: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Table modification
>
>
>
> >That said, if you look at the new revision control code, that may
> >provide some of the answe
>That said, if you look at the new revision control code, that may provide
>some of the answers (note that it's not all in CVS yet as I'm working on it
>at the moment).
Yes, I noticed you were working on revision control code. Revision control
is a great tool to perform upgrades. I doubt this is
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 02 October 2001 11:35
> To: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Table modification
>
>
>
> >As I said, that's how pg_dump does it afaict. The only case where it
> >(and
> >pg_dump) fails
>As I said, that's how pg_dump does it afaict. The only case where it (and
>pg_dump) fails that I've found so far is illustrated with
Again, I am still asking myself wether PostgreSQL schema objects should be
considered as 'compiled' or 'interpreted' code.
- If it is 'compiled' code, then sourc
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 02 October 2001 10:41
> To: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Table modification
>
>
>
> >This is the correct way to do it, though I appreciate your
> problem with
> >large tables. Pe
>This is the correct way to do it, though I appreciate your problem with
>large tables. Perhaps (for Table objects only) we should have a
>Tables.DeferRebuild property. When set true, all rebuilds triggered by mods
>of individual properties or collections will get queued up until an update
>metho
19 matches
Mail list logo
