pgaccess
Hello,
We are a small group around pgaccess and Teo (teo@flex.ro) who use pgaccess
in our daily work and now we try to join our efforts and bring our patches
together.
During the last two weeks we managed to arrange a web server, place there
pgaccess.org and the current web site that Teo was running on
www.flex.ro/pgaccess.
Now we are about to start a cvs and we are searching for the most recent
versions and patches of the code. We are searching also for everybody who is
using pgaccess and has wishes, or patches and wants to share them.
Please, everybody interested - contact us during the next few days. Next
week we are starting with what we have.
Iavor
--
www.pgaccess.org
Hello Ross,
Great to hear form you. We are just thinking what to do. There was one idea
to have a sourceforge cvs, another to have the cvs on the www.pgaccess.org
server. Then I found out that actually the pgaccess is in the PostgreSQL
distribution as well.
As for us the pgaccess is a tool for our daily work (we did some work on the
schema to visualize the databases better when working with one of our
clients) - we would be happy to have a distinctive location for everything -
such as www.pgaccess.org.
However if another solution would be better for any reason - I am personally
open and I believe all guys are open as well.
It is not important where it is - it is important (for us) to put a small
organization around the thing that can make collecting all patches possible.
Teo is pretty busy right now that's why he brought some of us who have
somehow recent patches together - so that we can see if something can come
out of that.
What's your feeling?
Iavor
--
www.pgaccess.org
Show quoted text
-----Original Message-----
From: Ross J. Reedstrom [mailto:reedstrm@rice.edu]
Sent: Thursday, May 09, 2002 5:43 PM
To: Iavor Raytchev
Subject: Re: [HACKERS] pgaccessHey there Iavor -
I wrote some patches to pgaccess, back a year or so ago: the schema
design editor was my work (mostly a clone of the query designer, with
some tweaks). I'd like to participate. Are you planning on keeping the
canonical version of the code in the main postgresql tree?Ross
--
Ross Reedstrom, Ph.D. reedstrm@rice.edu
Executive Director phone: 713-348-6166
Gulf Coast Consortium for Bioinformatics fax: 713-348-6182
Rice University MS-39
Houston, TX 77005
Import Notes
Reply to msg id not found: 20020509154240.GC26656@rice.edu | Resolved by subject fallback
...
It is not important where it is - it is important (for us) to put a small
organization around the thing that can make collecting all patches possible.
pgaccess is currently in the pgsql cvs tree, and is welcome to stay
there. Some of us have commit privileges, and y'all may want to have
someone else with privs also once you are organized and it is clear how
best to proceed. If you need web resources that can be arranged too, as
can a dedicated mailing list.
gborg is another way to organize, and of course www.pgaccess.org is a
way too. It partly depends on how you see the future of pgaccess. If it
stays tightly coupled to pgsql, then perhaps it may as way stay
organized with pgsql.
Regards.
- Thomas
On Thu, 9 May 2002, Thomas Lockhart wrote:
...
It is not important where it is - it is important (for us) to put a small
organization around the thing that can make collecting all patches possible.pgaccess is currently in the pgsql cvs tree, and is welcome to stay
there. Some of us have commit privileges, and y'all may want to have
someone else with privs also once you are organized and it is clear how
best to proceed. If you need web resources that can be arranged too, as
can a dedicated mailing list.gborg is another way to organize, and of course www.pgaccess.org is a
way too. It partly depends on how you see the future of pgaccess. If it
stays tightly coupled to pgsql, then perhaps it may as way stay
organized with pgsql.
I was working on the assumption that PgAccess was tightly coupled to postgres
[and versions of postgres] and since Teo was busy with other things and the PG
commiters were happy to apply patches that I would be submitting patches to the
postgres CVS.
I see no reason why pgaccess needs a separate repository, I presume it can be
fetched from the postgress CVS as a single entity. Although I haven't tried
this.
BTW, I had been wondering what to call the Schema tab now that that label is
required for schemas rather than design.
--
Nigel J. Andrews
Director
---
Logictree Systems Limited
Computer Consultants
On Thu, May 09, 2002 at 06:33:58PM +0100, Nigel J. Andrews wrote:
On Thu, 9 May 2002, Thomas Lockhart wrote:
gborg is another way to organize, and of course www.pgaccess.org is a
way too. It partly depends on how you see the future of pgaccess. If it
stays tightly coupled to pgsql, then perhaps it may as way stay
organized with pgsql.I was working on the assumption that PgAccess was tightly coupled to postgres
[and versions of postgres] and since Teo was busy with other things and the PG
commiters were happy to apply patches that I would be submitting patches to the
postgres CVS.
What we'll probably need is a note from teo to HACKERS, letting the CVS
commiters know who is 'approved' to bless pgaccess patches: i.e. their
patches should be commited, and they can bless third party patches.
I see no reason why pgaccess needs a separate repository, I presume it can be
fetched from the postgress CVS as a single entity. Although I haven't tried
this.
Works fine. Only tricky part would be providing the windows binary bits
(dlls) that have traditionally resided on teo's site.
BTW, I had been wondering what to call the Schema tab now that that label is
required for schemas rather than design.
If you check the archives, when I submitted that patch, I had the
forsight to ask if anyone could come up with a better name, forseeing
the collison that is happening today: no one came up with anything.
I agree it needs renaming. How about one of 'Charting', 'Graphing',
'Diagrams', 'Graphics', 'PrettyPictures', 'BossBait' ...
Ross
Nigel J. Andrews writes:
BTW, I had been wondering what to call the Schema tab now that that label is
required for schemas rather than design.
"Design"?
--
Peter Eisentraut peter_e@gmx.net
On Fri, May 10, 2002 at 09:13:20PM +0200, Peter Eisentraut wrote:
Nigel J. Andrews writes:
BTW, I had been wondering what to call the Schema tab now that that label is
required for schemas rather than design."Design"?
Thought about it, but it seems to 'active' for what's behind the tab:
drawing pretty pictures. There's no way to draw arbitrary tables and
create them, for example. Also, 'Design' is used a the button contrasting
to 'New' and 'Open' for things like the Table tab.
I think I'm leaning toward "Diagram", since that's the verb as well as
the noun. Hmm, on further inspection, all the tabs are plural nouns, so
"Designs" or "Diagrams", perhaps.
Ross
Nigel J. Andrews wrote:
gborg is another way to organize, and of course www.pgaccess.org is a
way too. It partly depends on how you see the future of pgaccess. If it
stays tightly coupled to pgsql, then perhaps it may as way stay
organized with pgsql.I see no reason why pgaccess needs a separate repository, I presume it can be
fetched from the postgress CVS as a single entity. Although I haven't tried
this.
[ Sorry, just catching up.]
You can easily checkout a subdirectory from CVS:
$ cvs checkout pgsql/src/bin/pgaccess
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026