Hi guys,
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 02 April 2003 01:50
To: [EMAIL PROTECTED]
Subject: Re: [pgadmin-hackers] pgadmin3 query tools
Here are my two cents. We put a view menu in BOTH our
tools.
That's not far from my solution,
Hi Frank,
It's rumoured that frank_lupo once said:
Hi Dave
There are many new functionalities for pgadmin2 that I would want to
develop.
I wonder if it has sense to make them or of it it is worth
the pain.
How much time will want that the pgadmin3 before to us
usable?
I see that the
Le Mercredi 2 Avril 2003 14:54, Dave Page a écrit :
What do you (and Mark, Jean-Michel, Keith, Andreas - and anyone else I
forgot) think?
Dear friends,
I don't have many things to say as I am not a contributor to pgAdmin3.
pgAdmin3 seems to be the future... You are doing a great job, I whish
Andreas,
That's old code. It's been namespaced for more than a month.
I just committed the changes that deal with that. Go ahead and update. Also
there is a bit more functionality on the QueryBuilder. I'll be spending most
of the day finishing up what I started. It should be mostly done by
Dave Page wrote:
Yup, certainly is. BTW, did you know that thanks to Frank Lupo, pga2 fully
supports Casts and Conversions in the schema now?
OK, message understood.
CAST, CONVERSION and OPERATOR CLASS are missing in pgadmin3 (yet). Any
more objects of your desire?
Centerfolds excepted.
frank_lupo wrote:
Hi Dave
There are many new functionalities for pgadmin2 that I would want to develop.
I wonder if it has sense to make them or of it it is worth the pain.
How much time will want that the pgadmin3 before to us usable?
I see that the development and much assets.
What I must
Dave Page wrote:
That's alright. Tom Lane explained why it wouldn't work in the backend
anyway...
Regards, Dave.
Dave,
maybe you got me wrong.
The CODING is already done... :-)
Regards,
Andreas
---(end of broadcast)---
TIP 1: subscribe and
Dave Page wrote:
That's fine with me. My major concern is that the code that drives the
grid is only written once. This is likely to get quite complex once
editting features are added, and I don't want to maintain 2 copies. I
always want to keep the look and feel consistant.
So, how about we
It's rumoured that Andreas Pflug once said:
Dave Page wrote:
That's alright. Tom Lane explained why it wouldn't work in the backend
anyway...
Regards, Dave.
Dave,
maybe you got me wrong.
The CODING is already done... :-)
No, I understood. I meant that it's OK you worked on it because
It's rumoured that Andreas Pflug once said:
Actually, I see YAQT (yet another query tool) for editing a table. You
just pick a table (maybe view), hit Edit and scroll up and down in
there. It must be capable of unlimited rows, which isn't easy but can
be done (I already implemented something
Hi Dave
There are many new functionalities for pgadmin2 that I would want to develop.
I wonder if it has sense to make them or of it it is worth the pain.
How much time will want that the pgadmin3 before to us usable?
I see that the development and much assets.
What I must make?
Bye !!
Frank
It's rumoured that Andreas Pflug once said:
Exactly. I've seen quite a lot of querying tools, and most of them were
quite ugly and at the edge of usability. For my experience, I think
two tool windows are the easiest way to handle it, not only in
concerning coding, but also regarding user
-Original Message-
From: frank_lupo [mailto:[EMAIL PROTECTED]
Sent: 03 April 2003 08:04
To: pgadmin-hackers
Subject: [pgadmin-hackers] problem compilation pgadmin2
Hi Dave
Ok finally they are successful to use cvs.
I have download the pgadmin2, pgschema and activex.
-Original Message-
From: frank_lupo [mailto:[EMAIL PROTECTED]
Sent: 03 April 2003 08:04
To: pgadmin-hackers
Subject: [pgadmin-hackers] problem compilation pgadmin2
Hi Dave
Ok finally they are successful to use cvs.
I have download the pgadmin2,
14 matches
Mail list logo