pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedNext release is 7.0(?)
21+ messages / 9 participants
[nested] [flat]
* Next release is 7.0(?)
@ 1999-10-09 12:53 Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 2 replies; 21+ messages in thread
From: Bruce Momjian @ 1999-10-09 12:53 UTC (permalink / raw)
To: PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-interfaces
Because the next release is going to probably be 7.0, if people have
backward compatability library code that they have been dying to remove,
this is the time for it.
I don't recommend removing backward compatability with 6.4 or 6.5
releases, but if you have some code that is hanging around just to be
compatible with 6.1 or earlier, I think it can be removed now.
--
Bruce Momjian | http://www.op.net/~candle
maillist@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
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Next release is 7.0(?)
@ 1999-10-09 13:03 Vince Vielhaber <vev@michvhf.com>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
1 sibling, 1 reply; 21+ messages in thread
From: Vince Vielhaber @ 1999-10-09 13:03 UTC (permalink / raw)
To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
On Sat, 9 Oct 1999, Bruce Momjian wrote:
> Because the next release is going to probably be 7.0, if people have
> backward compatability library code that they have been dying to remove,
> this is the time for it.
>
> I don't recommend removing backward compatability with 6.4 or 6.5
> releases, but if you have some code that is hanging around just to be
> compatible with 6.1 or earlier, I think it can be removed now.
>
>
Then perhaps we can also overhaul the installation. I installed about
5 times this past week and have it down to 4 or 5 steps (not including
regression testing).
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null
# include <std/disclaimers.h> Have you seen http://www.pop4.net?
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Next release is 7.0(?)
@ 1999-10-09 20:21 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Vince Vielhaber <vev@michvhf.com>
0 siblings, 1 reply; 21+ messages in thread
From: Bruce Momjian @ 1999-10-09 20:21 UTC (permalink / raw)
To: Vince Vielhaber <vev@michvhf.com>; +Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
> On Sat, 9 Oct 1999, Bruce Momjian wrote:
>
> > Because the next release is going to probably be 7.0, if people have
> > backward compatability library code that they have been dying to remove,
> > this is the time for it.
> >
> > I don't recommend removing backward compatability with 6.4 or 6.5
> > releases, but if you have some code that is hanging around just to be
> > compatible with 6.1 or earlier, I think it can be removed now.
> >
> >
>
> Then perhaps we can also overhaul the installation. I installed about
> 5 times this past week and have it down to 4 or 5 steps (not including
> regression testing).
Great. That certainly needs a cleanup. My ideal would be to have a
list of short instructions, and then have footnotes people would go to
when they had a problem with a certain item. Not sure how to do that in
sgml.
If we did it in html, they could click on something when they had a
problem, but html instructions are hard if you don't have a browser.
--
Bruce Momjian | http://www.op.net/~candle
maillist@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
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-10 18:01 Sergio A. Kessler <ser@perio.unlp.edu.ar>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
1 sibling, 1 reply; 21+ messages in thread
From: Sergio A. Kessler @ 1999-10-10 18:01 UTC (permalink / raw)
To: PostgreSQL-development <pgsql-hackers@postgreSQL.org>; +Cc: pgsql-interfaces
Bruce Momjian wrote:
>
> Because the next release is going to probably be 7.0, if people have
> backward compatability library code that they have been dying to remove,
> this is the time for it.
>
> I don't recommend removing backward compatability with 6.4 or 6.5
> releases, but if you have some code that is hanging around just to be
> compatible with 6.1 or earlier, I think it can be removed now.
can the commands createuser and destroyuser be renamed to
pg_createuser and pg_destroyuser (as pg_dump) adding soft links to
preserve backwards compatibility (declaring previous commands
deprecated) ?
the same can be done for createdb and destroydb ...
I think is a much more nice namespace for Postgres wich is
important when you have thousands of commands in this times.
--
| Sergio A. Kessler http://sak.org.ar
-O_O- You can have it Soon, Cheap, and Working; choose *two*.
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-10 20:39 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Sergio A. Kessler <ser@perio.unlp.edu.ar>
0 siblings, 1 reply; 21+ messages in thread
From: Bruce Momjian @ 1999-10-10 20:39 UTC (permalink / raw)
To: Sergio A. Kessler <ser@perio.unlp.edu.ar>; +Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-interfaces
Yes, we have discussed this, and will add it to the TODO list.
> Bruce Momjian wrote:
> >
> > Because the next release is going to probably be 7.0, if people have
> > backward compatability library code that they have been dying to remove,
> > this is the time for it.
> >
> > I don't recommend removing backward compatability with 6.4 or 6.5
> > releases, but if you have some code that is hanging around just to be
> > compatible with 6.1 or earlier, I think it can be removed now.
>
> can the commands createuser and destroyuser be renamed to
> pg_createuser and pg_destroyuser (as pg_dump) adding soft links to
> preserve backwards compatibility (declaring previous commands
> deprecated) ?
>
> the same can be done for createdb and destroydb ...
>
> I think is a much more nice namespace for Postgres wich is
> important when you have thousands of commands in this times.
>
> --
> | Sergio A. Kessler http://sak.org.ar
> -O_O- You can have it Soon, Cheap, and Working; choose *two*.
>
> ************
>
--
Bruce Momjian | http://www.op.net/~candle
maillist@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
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-11 15:17 Thomas Lockhart <lockhart@alumni.caltech.edu>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 2 replies; 21+ messages in thread
From: Thomas Lockhart @ 1999-10-11 15:17 UTC (permalink / raw)
To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: Sergio A. Kessler <ser@perio.unlp.edu.ar>; PostgreSQL-development <pgsql-hackers@postgresql.org>; pgsql-interfaces
> Yes, we have discussed this, and will add it to the TODO list.
> > can the commands createuser and destroyuser be renamed to
> > pg_createuser and pg_destroyuser (as pg_dump) adding soft links to
> > preserve backwards compatibility (declaring previous commands
> > deprecated) ?
> > the same can be done for createdb and destroydb ...
I hope we don't have a consensus on this. Long commands with
underscores in them are certainly another sign of the coming
apocalypse ;)
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-11 15:43 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
1 sibling, 3 replies; 21+ messages in thread
From: Bruce Momjian @ 1999-10-11 15:43 UTC (permalink / raw)
To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: Sergio A. Kessler <ser@perio.unlp.edu.ar>; PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-interfaces
> > Yes, we have discussed this, and will add it to the TODO list.
> > > can the commands createuser and destroyuser be renamed to
> > > pg_createuser and pg_destroyuser (as pg_dump) adding soft links to
> > > preserve backwards compatibility (declaring previous commands
> > > deprecated) ?
> > > the same can be done for createdb and destroydb ...
>
> I hope we don't have a consensus on this. Long commands with
> underscores in them are certainly another sign of the coming
> apocalypse ;)
But if we keep symlinks to the existing names, is that OK?
--
Bruce Momjian | http://www.op.net/~candle
maillist@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
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-11 16:56 Brook Milligan <brook@biology.nmsu.edu>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
2 siblings, 2 replies; 21+ messages in thread
From: Brook Milligan @ 1999-10-11 16:56 UTC (permalink / raw)
To: maillist@candle.pha.pa.us; +Cc: lockhart@alumni.caltech.edu; ser@perio.unlp.edu.ar; pgsql-hackers@postgreSQL.org; pgsql-interfaces
> I hope we don't have a consensus on this. Long commands with
> underscores in them are certainly another sign of the coming
> apocalypse ;)
But if we keep symlinks to the existing names, is that OK?
Isn't the point to avoid naming conflicts. Symlinks won't help that,
surely.
I agree; underscores are a pain. If you must go this direction, I
suggest hyphens (-).
Cheers,
Brook
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Next release is 7.0(?)
@ 1999-10-11 16:58 Brook Milligan <brook@biology.nmsu.edu>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 2 replies; 21+ messages in thread
From: Brook Milligan @ 1999-10-11 16:58 UTC (permalink / raw)
To: maillist@candle.pha.pa.us; +Cc: vev@michvhf.com; pgsql-hackers@postgreSQL.org
> Then perhaps we can also overhaul the installation. I installed about
> 5 times this past week and have it down to 4 or 5 steps (not including
> regression testing).
Would this also be a relevant time to get a regression test to run on
a non-installed system? Couldn't this be done by starting up the
database on a different port from within the newly compiled source
tree for the purpose of testing?
Cheers,
Brook
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-11 17:04 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Brook Milligan <brook@biology.nmsu.edu>
1 sibling, 1 reply; 21+ messages in thread
From: Bruce Momjian @ 1999-10-11 17:04 UTC (permalink / raw)
To: Brook Milligan <brook@biology.nmsu.edu>; +Cc: lockhart@alumni.caltech.edu; ser@perio.unlp.edu.ar; pgsql-hackers@postgreSQL.org; pgsql-interfaces
> > I hope we don't have a consensus on this. Long commands with
> > underscores in them are certainly another sign of the coming
> > apocalypse ;)
>
> But if we keep symlinks to the existing names, is that OK?
>
> Isn't the point to avoid naming conflicts. Symlinks won't help that,
> surely.
>
> I agree; underscores are a pain. If you must go this direction, I
> suggest hyphens (-).
You could make the actual command pg_createuser, and make a symlink of
createuser, but allow the symlink creation to fail. Best of both
worlds, I think. I vote for underscore. That's what I normally use.
Dashes look too much like command arguments.
--
Bruce Momjian | http://www.op.net/~candle
maillist@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
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Next release is 7.0(?)
@ 1999-10-11 17:05 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Brook Milligan <brook@biology.nmsu.edu>
1 sibling, 1 reply; 21+ messages in thread
From: Bruce Momjian @ 1999-10-11 17:05 UTC (permalink / raw)
To: Brook Milligan <brook@biology.nmsu.edu>; +Cc: vev@michvhf.com; pgsql-hackers@postgreSQL.org
> > Then perhaps we can also overhaul the installation. I installed about
> > 5 times this past week and have it down to 4 or 5 steps (not including
> > regression testing).
>
> Would this also be a relevant time to get a regression test to run on
> a non-installed system? Couldn't this be done by starting up the
> database on a different port from within the newly compiled source
> tree for the purpose of testing?
Gee, I never even though of that. What advantage would there be for
that?
--
Bruce Momjian | http://www.op.net/~candle
maillist@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
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Next release is 7.0(?)
@ 1999-10-11 18:05 Brook Milligan <brook@biology.nmsu.edu>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 0 replies; 21+ messages in thread
From: Brook Milligan @ 1999-10-11 18:05 UTC (permalink / raw)
To: maillist@candle.pha.pa.us; +Cc: vev@michvhf.com; pgsql-hackers@postgreSQL.org
> Would this also be a relevant time to get a regression test to run on
> a non-installed system? Couldn't this be done by starting up the
> database on a different port from within the newly compiled source
> tree for the purpose of testing?
Gee, I never even though of that. What advantage would there be for
that?
Wouldn't that be useful for developing/debugging/testing a new version
on a machine that runs some other version in production mode?
One example would be someone who wants to update, but wishes to verify
the functioning of the new version prior to blowing away the old
one. So, one could build the new version, run regression tests,
resolve any issues, THEN deinstall the old version and install the new
already verified one.
Another example is that developers could use a production machine to
tweak new code without having to actually install the test versions.
I'm sure other applications of that flexibility are apparent also.
Cheers,
Brook
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Next release is 7.0(?)
@ 1999-10-11 18:06 James Thompson <jamest@math.ksu.edu>
parent: Brook Milligan <brook@biology.nmsu.edu>
1 sibling, 1 reply; 21+ messages in thread
From: James Thompson @ 1999-10-11 18:06 UTC (permalink / raw)
To: Brook Milligan <brook@biology.nmsu.edu>; +Cc: maillist@candle.pha.pa.us; vev@michvhf.com; pgsql-hackers@postgreSQL.org
On Mon, 11 Oct 1999, Brook Milligan wrote:
> Then perhaps we can also overhaul the installation. I installed about
> 5 times this past week and have it down to 4 or 5 steps (not including
> regression testing).
>
One thing I thought would be nice would be a client only install. Say I'm
running a server on Solaris and want to make psql available on linux
stations which will access the Solaris server. Right now, unless I've
missed something, I'm stuck installing the whole package. No big problem
but if you're overhaulling the install..... :-)
Take Care,
James
->->->->->->->->->->->->->->->->->->---<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<
James Thompson 138 Cardwell Hall Manhattan, Ks 66506 785-532-0561
Kansas State University Department of Mathematics
->->->->->->->->->->->->->->->->->->---<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Next release is 7.0(?)
@ 1999-10-11 18:32 Lamar Owen <lamar.owen@wgcr.org>
parent: James Thompson <jamest@math.ksu.edu>
0 siblings, 0 replies; 21+ messages in thread
From: Lamar Owen @ 1999-10-11 18:32 UTC (permalink / raw)
To: James Thompson <jamest@math.ksu.edu>; +Cc: Brook Milligan <brook@biology.nmsu.edu>; maillist@candle.pha.pa.us; vev@michvhf.com; pgsql-hackers@postgreSQL.org
James Thompson wrote:
>
> One thing I thought would be nice would be a client only install. Say I'm
> running a server on Solaris and want to make psql available on linux
> stations which will access the Solaris server. Right now, unless I've
> missed something, I'm stuck installing the whole package. No big problem
> but if you're overhaulling the install..... :-)
You can do that now with the RPM installation under RedHat Linux --
however, it is an RPM feature, not part of the tarball.
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-11 20:31 Sergio A. Kessler <ser@perio.unlp.edu.ar>
parent: Brook Milligan <brook@biology.nmsu.edu>
1 sibling, 1 reply; 21+ messages in thread
From: Sergio A. Kessler @ 1999-10-11 20:31 UTC (permalink / raw)
To: Brook Milligan <brook@biology.nmsu.edu>; +Cc: maillist@candle.pha.pa.us; lockhart@alumni.caltech.edu; pgsql-hackers@postgreSQL.org; pgsql-interfaces
Brook Milligan wrote:
>
> > I hope we don't have a consensus on this. Long commands with
> > underscores in them are certainly another sign of the coming
> > apocalypse ;)
>
> But if we keep symlinks to the existing names, is that OK?
>
> Isn't the point to avoid naming conflicts. Symlinks won't help that,
> surely.
my suggestion was:
in 7.0: provide symlinks for backward compatibility and make big
warnings 'don't use createuser, etc. they are deprecated'
all over the place ...
in 7.1: remove the symlinks.
> I agree; underscores are a pain. If you must go this direction, I
> suggest hyphens (-).
yup, but maybe (-) can rise problems in some filesystems ...
(I certainly don't know)
and more importantly you have then to rename pg_dump and pg_dumpall
wich is the more heavily used command in scripts ...
my idea was to leave this commands untouched.
as for longnames that Thomas doesn't like (wich I don't agree because
my idea for upgrading scripts is just: 'prepend a pg_ to the commands')
what about pg_adduser, pg_deluser, pg_adddb, etc ? ;)
--
| Sergio A. Kessler http://sak.org.ar
-O_O- You can have it Soon, Cheap, and Working; choose *two*.
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-11 20:51 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Sergio A. Kessler <ser@perio.unlp.edu.ar>
0 siblings, 0 replies; 21+ messages in thread
From: Bruce Momjian @ 1999-10-11 20:51 UTC (permalink / raw)
To: Sergio A. Kessler <ser@perio.unlp.edu.ar>; +Cc: Brook Milligan <brook@biology.nmsu.edu>; lockhart@alumni.caltech.edu; pgsql-hackers@postgreSQL.org; pgsql-interfaces
> my suggestion was:
> in 7.0: provide symlinks for backward compatibility and make big
> warnings 'don't use createuser, etc. they are deprecated'
> all over the place ...
> in 7.1: remove the symlinks.
>
> > I agree; underscores are a pain. If you must go this direction, I
> > suggest hyphens (-).
>
> yup, but maybe (-) can rise problems in some filesystems ...
> (I certainly don't know)
> and more importantly you have then to rename pg_dump and pg_dumpall
> wich is the more heavily used command in scripts ...
> my idea was to leave this commands untouched.
>
> as for longnames that Thomas doesn't like (wich I don't agree because
> my idea for upgrading scripts is just: 'prepend a pg_ to the commands')
> what about pg_adduser, pg_deluser, pg_adddb, etc ? ;)
That's a compromise. The destroy* entries are from the old quel days.
Of course, that would make pg_deluser into pg_dropuser, but adddb would
be createdb, and we are back were we started. :-)
--
Bruce Momjian | http://www.op.net/~candle
maillist@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
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-12 04:16 The Hermit Hacker <scrappy@hub.org>
parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
1 sibling, 0 replies; 21+ messages in thread
From: The Hermit Hacker @ 1999-10-12 04:16 UTC (permalink / raw)
To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: Bruce Momjian <maillist@candle.pha.pa.us>; Sergio A. Kessler <ser@perio.unlp.edu.ar>; PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-interfaces
On Mon, 11 Oct 1999, Thomas Lockhart wrote:
> > Yes, we have discussed this, and will add it to the TODO list.
> > > can the commands createuser and destroyuser be renamed to
> > > pg_createuser and pg_destroyuser (as pg_dump) adding soft links to
> > > preserve backwards compatibility (declaring previous commands
> > > deprecated) ?
> > > the same can be done for createdb and destroydb ...
>
> I hope we don't have a consensus on this. Long commands with
> underscores in them are certainly another sign of the coming
> apocalypse ;)
You'll get my agreement on this...but, then again, I'm advocating getting
rid of them altoghther and forcing the DBA to be forced to learn teh
proper commands...*shrug*
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-12 04:17 The Hermit Hacker <scrappy@hub.org>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
2 siblings, 0 replies; 21+ messages in thread
From: The Hermit Hacker @ 1999-10-12 04:17 UTC (permalink / raw)
To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>; Sergio A. Kessler <ser@perio.unlp.edu.ar>; PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-interfaces
On Mon, 11 Oct 1999, Bruce Momjian wrote:
> > > Yes, we have discussed this, and will add it to the TODO list.
> > > > can the commands createuser and destroyuser be renamed to
> > > > pg_createuser and pg_destroyuser (as pg_dump) adding soft links to
> > > > preserve backwards compatibility (declaring previous commands
> > > > deprecated) ?
> > > > the same can be done for createdb and destroydb ...
> >
> > I hope we don't have a consensus on this. Long commands with
> > underscores in them are certainly another sign of the coming
> > apocalypse ;)
>
> But if we keep symlinks to the existing names, is that OK?
can we get rid of 'createdb/destroydb' and shorten them to:
'pg_adddb/pg_deldb' ... ? :)
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-12 04:18 The Hermit Hacker <scrappy@hub.org>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
2 siblings, 1 reply; 21+ messages in thread
From: The Hermit Hacker @ 1999-10-12 04:18 UTC (permalink / raw)
To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>; Sergio A. Kessler <ser@perio.unlp.edu.ar>; PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-interfaces
On Mon, 11 Oct 1999, Bruce Momjian wrote:
> > > Yes, we have discussed this, and will add it to the TODO list.
> > > > can the commands createuser and destroyuser be renamed to
> > > > pg_createuser and pg_destroyuser (as pg_dump) adding soft links to
> > > > preserve backwards compatibility (declaring previous commands
> > > > deprecated) ?
> > > > the same can be done for createdb and destroydb ...
> >
> > I hope we don't have a consensus on this. Long commands with
> > underscores in them are certainly another sign of the coming
> > apocalypse ;)
>
> But if we keep symlinks to the existing names, is that OK?
Oh, and, IMHO...remove, don't create symlinks...its a major release, we
don't have to maintain backwards compatability...we aren't mIcrosoft, eh?
:)
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-12 13:58 Bruce Momjian <maillist@candle.pha.pa.us>
parent: The Hermit Hacker <scrappy@hub.org>
0 siblings, 0 replies; 21+ messages in thread
From: Bruce Momjian @ 1999-10-12 13:58 UTC (permalink / raw)
To: The Hermit Hacker <scrappy@hub.org>; +Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>; Sergio A. Kessler <ser@perio.unlp.edu.ar>; PostgreSQL-development <pgsql-hackers@postgreSQL.org>; pgsql-interfaces
> > > I hope we don't have a consensus on this. Long commands with
> > > underscores in them are certainly another sign of the coming
> > > apocalypse ;)
> >
> > But if we keep symlinks to the existing names, is that OK?
>
> Oh, and, IMHO...remove, don't create symlinks...its a major release, we
> don't have to maintain backwards compatability...we aren't mIcrosoft, eh?
> :)
That is a good point. We could remove them. They don't get called very
often.
--
Bruce Momjian | http://www.op.net/~candle
maillist@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
^ permalink raw reply [nested|flat] 21+ messages in thread
* Re: [HACKERS] Re: [INTERFACES] Next release is 7.0(?)
@ 1999-10-12 23:13 Craig Orsinger <orsingerc@epg-gw1.lewis.army.mil>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 0 replies; 21+ messages in thread
From: Craig Orsinger @ 1999-10-12 23:13 UTC (permalink / raw)
To: pgsql-interfaces; +Cc: pgsql-hackers@postgreSQL.org
On 11-Oct-99 Bruce Momjian wrote:
> You could make the actual command pg_createuser, and make a symlink of
> createuser, but allow the symlink creation to fail. Best of both
> worlds, I think. I vote for underscore. That's what I normally use.
> Dashes look too much like command arguments.
Agreed. I don't like underscores, but hyphens can be worse.
I think the best idea is to use a name that identifies the script as
being a part of PostgreSQL, and can somehow clearly define what the
script is designed to do, and then whatever you choose, _stick_with_it_!
System administrators and programmers can make symbolic links if they
need them.
----------------------------------
Date: 12-Oct-99 Time: 16:10:10
Craig Orsinger (email: <orsingerc@epg-gw1.lewis.army.mil>)
Logicon RDA
Bldg. 8B28 "Just another megalomaniac with ideas above his
6th & F Streets station. The Universe is full of them."
Ft. Lewis, WA 98433 - The Doctor
----------------------------------
^ permalink raw reply [nested|flat] 21+ messages in thread
end of thread, other threads:[~1999-10-12 23:13 UTC | newest]
Thread overview: 21+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-10-09 12:53 Next release is 7.0(?) Bruce Momjian <maillist@candle.pha.pa.us>
1999-10-09 13:03 ` Vince Vielhaber <vev@michvhf.com>
1999-10-09 20:21 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-10-11 16:58 ` Brook Milligan <brook@biology.nmsu.edu>
1999-10-11 17:05 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-10-11 18:05 ` Brook Milligan <brook@biology.nmsu.edu>
1999-10-11 18:06 ` James Thompson <jamest@math.ksu.edu>
1999-10-11 18:32 ` Lamar Owen <lamar.owen@wgcr.org>
1999-10-10 18:01 ` Sergio A. Kessler <ser@perio.unlp.edu.ar>
1999-10-10 20:39 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-10-11 15:17 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-10-11 15:43 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-10-11 16:56 ` Brook Milligan <brook@biology.nmsu.edu>
1999-10-11 17:04 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-10-12 23:13 ` Craig Orsinger <orsingerc@epg-gw1.lewis.army.mil>
1999-10-11 20:31 ` Sergio A. Kessler <ser@perio.unlp.edu.ar>
1999-10-11 20:51 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-10-12 04:17 ` The Hermit Hacker <scrappy@hub.org>
1999-10-12 04:18 ` The Hermit Hacker <scrappy@hub.org>
1999-10-12 13:58 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-10-12 04:16 ` The Hermit Hacker <scrappy@hub.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox