> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 24 February 2002 23:07
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: Working oin pgAdmin2
>
>
> > I think the most effective way to go would be to write new cl
> I prefer crepes (au chocolat - is that right? It's about 14 years since I
> did French at school), but that's just me :-)
Don't hesitate to practice and visit me with your wife.
> I think the most effective way to go would be to write new classes
> pgSchema.ODBCServer, pgSchema.ODBCTables, pgSc
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 24 February 2002 21:23
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Working oin pgAdmin2
>
>
> Le Dimanche 24 Février 2002 21:19, Dave Page a
Le Dimanche 24 Février 2002 21:19, Dave Page a écrit :
> If a developer working on pgSchema cannot code the required SQL, then this
> is *not* the project for him to be hacking. That's like a cowboy who can't
> use a lassoo...
Let's say a French man without a baguette. Oh, now I see...
IMHO, thi
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 24 February 2002 08:47
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Working oin pgAdmin2
>
>
> Dear Dave,
>
> I got rid of manual SQL constructions in pgSchema-&
Dear Dave,
I got rid of manual SQL constructions in pgSchema->Views, just for testing
and demonstration. Don't kill me, the job is more or less clean.
This demonstrates we could easily "mask" all SQL in pgSchema->Tables,
Triggers, etc... And it could be possible to do the same in pgAdmin2. Thi
