You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(21) |
Nov
(47) |
Dec
(26) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(152) |
Feb
(216) |
Mar
(53) |
Apr
(50) |
May
(34) |
Jun
(14) |
Jul
(69) |
Aug
(27) |
Sep
(86) |
Oct
(36) |
Nov
(23) |
Dec
(61) |
2003 |
Jan
(100) |
Feb
(50) |
Mar
(94) |
Apr
(48) |
May
(127) |
Jun
(102) |
Jul
(64) |
Aug
(65) |
Sep
(68) |
Oct
(57) |
Nov
(43) |
Dec
(68) |
2004 |
Jan
(39) |
Feb
(41) |
Mar
(84) |
Apr
(21) |
May
(115) |
Jun
(102) |
Jul
(125) |
Aug
(79) |
Sep
(65) |
Oct
(44) |
Nov
(66) |
Dec
(31) |
2005 |
Jan
(65) |
Feb
(51) |
Mar
(117) |
Apr
(50) |
May
(61) |
Jun
(24) |
Jul
(42) |
Aug
(52) |
Sep
(16) |
Oct
(21) |
Nov
(48) |
Dec
(9) |
2006 |
Jan
(15) |
Feb
(5) |
Mar
(8) |
Apr
(1) |
May
(33) |
Jun
(47) |
Jul
(103) |
Aug
(36) |
Sep
(1) |
Oct
(25) |
Nov
(11) |
Dec
(5) |
2007 |
Jan
(19) |
Feb
(12) |
Mar
(12) |
Apr
(61) |
May
(9) |
Jun
(66) |
Jul
(47) |
Aug
(12) |
Sep
(23) |
Oct
(13) |
Nov
(24) |
Dec
(12) |
2008 |
Jan
(4) |
Feb
(16) |
Mar
(3) |
Apr
(1) |
May
(2) |
Jun
(15) |
Jul
(2) |
Aug
(2) |
Sep
(3) |
Oct
(20) |
Nov
(7) |
Dec
(25) |
2009 |
Jan
(5) |
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
(12) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
2010 |
Jan
(1) |
Feb
|
Mar
(44) |
Apr
(15) |
May
(51) |
Jun
(30) |
Jul
(38) |
Aug
(43) |
Sep
(34) |
Oct
(9) |
Nov
(31) |
Dec
(15) |
2011 |
Jan
(15) |
Feb
(3) |
Mar
(9) |
Apr
(4) |
May
(53) |
Jun
(45) |
Jul
(4) |
Aug
(11) |
Sep
(2) |
Oct
(8) |
Nov
(3) |
Dec
(3) |
2012 |
Jan
(1) |
Feb
(1) |
Mar
(5) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(14) |
Oct
(6) |
Nov
(5) |
Dec
(1) |
2013 |
Jan
(32) |
Feb
(26) |
Mar
(19) |
Apr
(46) |
May
(55) |
Jun
(37) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
2014 |
Jan
|
Feb
(7) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: Karl O. P. <ko...@me...> - 2013-04-20 14:11:29
|
On 04/20/2013 08:04:04 AM, Jehan-Guillaume (ioguix) de Rorthais wrote: > On 20/04/2013 00:03, Hans Chen wrote: > > Hi > > > > I am considering to add function to change position of columns in > > table. > > I am not sure to understand clearly what you want to achieve. > PostgreSQL > doesn't supports "changing" columns position. Some thoughts.... No, it's not supported by pg but that does not mean it might not be useful, and I've had related thoughts along similar lines. (The "browse" feature is reasonably useless for anything other than a general overview of what's in the table, for example, since it does not sort the rows. So, it'd be nice to be able to allow each individual user a way to configure how they want each table sorted. Of course clustering is also an option. But I think that's mixing performance tuning with user interface.) Anyhow you could re-order table columns by saving the table's data, re-creating the table, and transferring the data into it. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Jehan-Guillaume (i. de R. <io...@fr...> - 2013-04-20 13:26:12
|
On 19/04/2013 23:46, Hans Chen wrote: > On Fri, Apr 19, 2013 at 4:52 PM, Robert Treat <ro...@xz...> wrote: >> >> On Fri, Apr 19, 2013 at 10:14 AM, Karl O. Pinc <ko...@me...> wrote: >>> On 04/18/2013 10:09:30 PM, Robert Treat wrote: >>>> On Thu, Apr 18, 2013 at 2:26 PM, Karl O. Pinc <ko...@me...> wrote: >>>>> On 04/18/2013 10:47:35 AM, Hans Chen wrote: >>> >>>>>> * Add support for default db to connect to on login page (we had >>>>>> several >>>>>> users complaining about that lately) >>> >>>>> I'd think the default >>>>> would go in the config file as another config parameter, >>>>> but if you've a different idea it might be good to discuss >>>>> it ahead of time. >>>>> >>>> >>>> Actually, a better feature would be one I had started dabbling with, >>>> which I called "libpq_login". The basic idea was that you could set >>>> libpq_login to true in the config, and instead of displaying the >>>> normal sets of servers, instead we would show a login box where you >>>> could enter user, host, database, port type information, or >>>> alternatively a url formatted libpq connect string. >>> >>> I don't see this as a substitute for having a default server >>> and thereby having the "home page" start by asking for username >>> and password. The whole point, to my way of thinking, is that >>> the user not have to think about the server at all. I don't know, >>> but I'd guess that a lot of installations have just a single server. >>> >> >> That's fair. If there is demand for the default server login, it's >> probably simpler to implement. >> > > I am little curious what is the complain from users. Seems current way > is not bad if only single server. Some user would like to be able to connect directly on a given database, not to the defaultdb given in the conf file. >>>> This would allow >>>> people to be able to login without having to be able to get access to >>>> the command line to configure every server. >>> >>> By this you mean without having to edit the ppa config file? >>> >>> I agree it would be nice to not be limited to the servers >>> listed in the config file. There's a temptation to want >>> to be able to put some limits on what servers could be >>> reached so as to avoid an "open relay" sort of situation. >>> But I think it'd be best to avoid over-design at this point. >>> >> >> Yeah... I've mostly seen this from people running in the cloud, or >> doing heroku type stuff, where the connection credentials seem to be >> more fluid. > > A connection string like : pg://user:password@server:port/database is > cool. May I start from it? It already exists since PostgreSQL 9.1. See : http://www.postgresql.org/docs/current/interactive/libpq-connect.html#LIBPQ-CONNSTRING So if Robert is adding a form to connect to a database using a libpq connection string, then this syntax will be automatically supported. I see no point to adding this with some parsing pain inside PPA though. >> Robert Treat >> conjecture: xzilla.net >> consulting: omniti.com > > Best Regards, > > Hans Chen |
From: Jehan-Guillaume (i. de R. <io...@fr...> - 2013-04-20 13:06:22
|
On 20/04/2013 00:35, Karl O. Pinc wrote: > On 04/19/2013 05:03:58 PM, Hans Chen wrote: > >> I may add two buttons (up and down) to table view. > > If you are considering changes to the page that > shows all the tables in a schema then please write > before starting work. I'll do the same since I'm > planning on working on this part of the code. I think you are not talking about the same things at all. AFAIU, Hans is talking about columns in the table, you are talking about tables in a schema. > Once I start I should be able to finish pretty quickly. > > I'm thinking about working on this next Tuesday. Please, could you create a new thread to talk about your idea ? > Karl <ko...@me...> > Free Software: "You don't pay back, you pay forward." > -- Robert A. Heinlein |
From: Jehan-Guillaume (i. de R. <io...@fr...> - 2013-04-20 13:04:15
|
On 20/04/2013 00:03, Hans Chen wrote: > Hi > > I am considering to add function to change position of columns in > table. I am not sure to understand clearly what you want to achieve. PostgreSQL doesn't supports "changing" columns position. > Have tested to modify value of attnum in pg_attribute is a > possible solution. Then you probably corrupt your database in some ways in guess. You should never issue write queries to the catalog. > I may add two buttons (up and down) to table view. > > let me know what is your suggestions. If you really want to move your columns position, then create a view. BTW, why do you want to move your table columns in the first place ? > > Best Regards, > > Hans Chen |
From: Karl O. P. <ko...@me...> - 2013-04-20 12:42:30
|
On 04/20/2013 07:01:12 AM, Hans Chen wrote: > No, I am going to change the the page show all columns of table. Ok. Thanks. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Hans C. <ha...@gm...> - 2013-04-20 12:01:20
|
On Saturday, April 20, 2013, Karl O. Pinc wrote: > On 04/19/2013 05:03:58 PM, Hans Chen wrote: > > > I may add two buttons (up and down) to table view. > > If you are considering changes to the page that > shows all the tables in a schema then please write > before starting work. I'll do the same since I'm > planning on working on this part of the code. > > Once I start I should be able to finish pretty quickly. > > I'm thinking about working on this next Tuesday. > > No, I am going to change the the page show all columns of table. > > Karl <ko...@me...> > Free Software: "You don't pay back, you pay forward." > -- Robert A. Heinlein > > -- Sent from Gmail Mobile |
From: Karl O. P. <ko...@me...> - 2013-04-19 22:36:59
|
On 04/19/2013 04:46:37 PM, Hans Chen wrote: > On Fri, Apr 19, 2013 at 4:52 PM, Robert Treat <ro...@xz...> wrote: > > > > On Fri, Apr 19, 2013 at 10:14 AM, Karl O. Pinc <ko...@me...> > wrote: > > > On 04/18/2013 10:09:30 PM, Robert Treat wrote: > > >> On Thu, Apr 18, 2013 at 2:26 PM, Karl O. Pinc <ko...@me...> > wrote: > > >> > On 04/18/2013 10:47:35 AM, Hans Chen wrote: > > > > > >> >> * Add support for default db to connect to on login page (we > had > > >> >> several > > >> >> users complaining about that lately) > > > I don't see this as a substitute for having a default server > > > and thereby having the "home page" start by asking for username > > > and password. The whole point, to my way of thinking, is that > > > the user not have to think about the server at all. I don't > know, > > > but I'd guess that a lot of installations have just a single > server. > > > > > > > That's fair. If there is demand for the default server login, it's > > probably simpler to implement. > > > > I am little curious what is the complain from users. Seems current > way > is not bad if only single server. Well, I've a lot of users that don't want to have to think about the server. They can be trained to click on it, but you have to train them to click on it. It'd be nice not to have to do this. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Karl O. P. <ko...@me...> - 2013-04-19 22:35:38
|
On 04/19/2013 05:03:58 PM, Hans Chen wrote: > I may add two buttons (up and down) to table view. If you are considering changes to the page that shows all the tables in a schema then please write before starting work. I'll do the same since I'm planning on working on this part of the code. Once I start I should be able to finish pretty quickly. I'm thinking about working on this next Tuesday. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Hans C. <ha...@gm...> - 2013-04-19 22:04:25
|
Hi I am considering to add function to change position of columns in table. Have tested to modify value of attnum in pg_attribute is a possible solution. I may add two buttons (up and down) to table view. let me know what is your suggestions. Best Regards, Hans Chen |
From: Hans C. <ha...@gm...> - 2013-04-19 21:47:05
|
On Fri, Apr 19, 2013 at 4:52 PM, Robert Treat <ro...@xz...> wrote: > > On Fri, Apr 19, 2013 at 10:14 AM, Karl O. Pinc <ko...@me...> wrote: > > On 04/18/2013 10:09:30 PM, Robert Treat wrote: > >> On Thu, Apr 18, 2013 at 2:26 PM, Karl O. Pinc <ko...@me...> wrote: > >> > On 04/18/2013 10:47:35 AM, Hans Chen wrote: > > > >> >> * Add support for default db to connect to on login page (we had > >> >> several > >> >> users complaining about that lately) > > > >> > I'd think the default > >> > would go in the config file as another config parameter, > >> > but if you've a different idea it might be good to discuss > >> > it ahead of time. > >> > > >> > >> Actually, a better feature would be one I had started dabbling with, > >> which I called "libpq_login". The basic idea was that you could set > >> libpq_login to true in the config, and instead of displaying the > >> normal sets of servers, instead we would show a login box where you > >> could enter user, host, database, port type information, or > >> alternatively a url formatted libpq connect string. > > > > I don't see this as a substitute for having a default server > > and thereby having the "home page" start by asking for username > > and password. The whole point, to my way of thinking, is that > > the user not have to think about the server at all. I don't know, > > but I'd guess that a lot of installations have just a single server. > > > > That's fair. If there is demand for the default server login, it's > probably simpler to implement. > I am little curious what is the complain from users. Seems current way is not bad if only single server. > > >> This would allow > >> people to be able to login without having to be able to get access to > >> the command line to configure every server. > > > > By this you mean without having to edit the ppa config file? > > > > I agree it would be nice to not be limited to the servers > > listed in the config file. There's a temptation to want > > to be able to put some limits on what servers could be > > reached so as to avoid an "open relay" sort of situation. > > But I think it'd be best to avoid over-design at this point. > > > > Yeah... I've mostly seen this from people running in the cloud, or > doing heroku type stuff, where the connection credentials seem to be > more fluid. A connection string like : pg://user:password@server:port/database is cool. May I start from it? > > Robert Treat > conjecture: xzilla.net > consulting: omniti.com Best Regards, Hans Chen |
From: Robert T. <ro...@xz...> - 2013-04-19 14:53:04
|
On Fri, Apr 19, 2013 at 10:14 AM, Karl O. Pinc <ko...@me...> wrote: > On 04/18/2013 10:09:30 PM, Robert Treat wrote: >> On Thu, Apr 18, 2013 at 2:26 PM, Karl O. Pinc <ko...@me...> wrote: >> > On 04/18/2013 10:47:35 AM, Hans Chen wrote: > >> >> * Add support for default db to connect to on login page (we had >> >> several >> >> users complaining about that lately) > >> > I'd think the default >> > would go in the config file as another config parameter, >> > but if you've a different idea it might be good to discuss >> > it ahead of time. >> > >> >> Actually, a better feature would be one I had started dabbling with, >> which I called "libpq_login". The basic idea was that you could set >> libpq_login to true in the config, and instead of displaying the >> normal sets of servers, instead we would show a login box where you >> could enter user, host, database, port type information, or >> alternatively a url formatted libpq connect string. > > I don't see this as a substitute for having a default server > and thereby having the "home page" start by asking for username > and password. The whole point, to my way of thinking, is that > the user not have to think about the server at all. I don't know, > but I'd guess that a lot of installations have just a single server. > That's fair. If there is demand for the default server login, it's probably simpler to implement. >> This would allow >> people to be able to login without having to be able to get access to >> the command line to configure every server. > > By this you mean without having to edit the ppa config file? > > I agree it would be nice to not be limited to the servers > listed in the config file. There's a temptation to want > to be able to put some limits on what servers could be > reached so as to avoid an "open relay" sort of situation. > But I think it'd be best to avoid over-design at this point. > Yeah... I've mostly seen this from people running in the cloud, or doing heroku type stuff, where the connection credentials seem to be more fluid. Robert Treat conjecture: xzilla.net consulting: omniti.com |
From: Karl O. P. <ko...@me...> - 2013-04-19 14:15:08
|
On 04/18/2013 10:09:30 PM, Robert Treat wrote: > On Thu, Apr 18, 2013 at 2:26 PM, Karl O. Pinc <ko...@me...> wrote: > > On 04/18/2013 10:47:35 AM, Hans Chen wrote: > >> * Add support for default db to connect to on login page (we had > >> several > >> users complaining about that lately) > > I'd think the default > > would go in the config file as another config parameter, > > but if you've a different idea it might be good to discuss > > it ahead of time. > > > > Actually, a better feature would be one I had started dabbling with, > which I called "libpq_login". The basic idea was that you could set > libpq_login to true in the config, and instead of displaying the > normal sets of servers, instead we would show a login box where you > could enter user, host, database, port type information, or > alternatively a url formatted libpq connect string. I don't see this as a substitute for having a default server and thereby having the "home page" start by asking for username and password. The whole point, to my way of thinking, is that the user not have to think about the server at all. I don't know, but I'd guess that a lot of installations have just a single server. > This would allow > people to be able to login without having to be able to get access to > the command line to configure every server. By this you mean without having to edit the ppa config file? I agree it would be nice to not be limited to the servers listed in the config file. There's a temptation to want to be able to put some limits on what servers could be reached so as to avoid an "open relay" sort of situation. But I think it'd be best to avoid over-design at this point. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Robert T. <ro...@xz...> - 2013-04-19 03:09:37
|
On Thu, Apr 18, 2013 at 2:26 PM, Karl O. Pinc <ko...@me...> wrote: > On 04/18/2013 10:47:35 AM, Hans Chen wrote: >> All >> >> May I know detailed requirements about this item in TODO: >> >> * Add support for default db to connect to on login page (we had >> several >> users complaining about that lately) >> >> I would like to do something for that. > > You can talk about it on IRC at #phppgadmin on irc.freenode.net. > Or just send a patch to this list. I'd think the default > would go in the config file as another config parameter, > but if you've a different idea it might be good to discuss > it ahead of time. > Actually, a better feature would be one I had started dabbling with, which I called "libpq_login". The basic idea was that you could set libpq_login to true in the config, and instead of displaying the normal sets of servers, instead we would show a login box where you could enter user, host, database, port type information, or alternatively a url formatted libpq connect string. This would allow people to be able to login without having to be able to get access to the command line to configure every server. There are some tricky pieces around connection variable passing, and also what to do about bin paths and similar things, but I think it should be doable. Robert Treat play: xzilla.net work: omniti.com |
From: Karl O. P. <ko...@me...> - 2013-04-18 18:26:56
|
On 04/18/2013 10:47:35 AM, Hans Chen wrote: > All > > May I know detailed requirements about this item in TODO: > > * Add support for default db to connect to on login page (we had > several > users complaining about that lately) > > I would like to do something for that. You can talk about it on IRC at #phppgadmin on irc.freenode.net. Or just send a patch to this list. I'd think the default would go in the config file as another config parameter, but if you've a different idea it might be good to discuss it ahead of time. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Hans C. <ha...@gm...> - 2013-04-18 15:48:02
|
All May I know detailed requirements about this item in TODO: * Add support for default db to connect to on login page (we had several users complaining about that lately) I would like to do something for that. Best Regards, Hans Chen |
From: Christoph B. <my...@de...> - 2013-04-18 11:04:43
|
Hi, here's a wishlist item from a Debian user. The table name is visible in the breadcrumbs, though it would be nice if the box just below that would say "Browse $table" instead of just "Browse". http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683071 ----- Forwarded message from Csanyi Pal <csa...@gm...> ----- Date: Sat, 28 Jul 2012 14:24:59 +0200 From: Csanyi Pal <csa...@gm...> Reply-To: Csanyi Pal <csa...@gm...>, 68...@bu... To: su...@bu... Subject: Bug#683071: [phppgadmin] To have Table Name displayed when Browse the Table Package: phppgadmin Version: 5.0.4-1 Severity: wishlist --- Please enter the report below this line. --- When one browse a table in a database the data of that table are displayed in rows and columns of that table. I wish to have displayed the Table Name above rows so one can see it right away. At present one must to search Table Name in the Link line above. ----- End forwarded message ----- Christoph -- cb...@df... | http://www.df7cb.de/ |
From: Robert T. <ro...@xz...> - 2013-04-16 11:51:58
|
On Mon, Apr 15, 2013 at 9:59 PM, Karl O. Pinc <ko...@me...> wrote: > On 04/14/2013 06:40:30 PM, Robert Treat wrote: > >> I'd like to get some independent confirmation that the packages look >> ok before I start sending announcements out to the world. Thanks in >> advance, > > I configured it and it seems to run against pg-dev (head as of > Sunday). I don't seem to get any errors doing random bits of > this and that. Nothing at all comprehensive. > > And I haven't really _looked_ at the files to see if something's > missing. > > If there's something specific you want me to test I can, but > I'm about to disappear for 24 hours. > Nope, I think we're good. Thanks. Robert Treat conjecture: xzilla.net consulting: omniti.com |
From: Karl O. P. <ko...@me...> - 2013-04-16 02:00:01
|
On 04/14/2013 06:40:30 PM, Robert Treat wrote: > I'd like to get some independent confirmation that the packages look > ok before I start sending announcements out to the world. Thanks in > advance, I configured it and it seems to run against pg-dev (head as of Sunday). I don't seem to get any errors doing random bits of this and that. Nothing at all comprehensive. And I haven't really _looked_ at the files to see if something's missing. If there's something specific you want me to test I can, but I'm about to disappear for 24 hours. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Robert T. <ro...@xz...> - 2013-04-15 20:49:08
|
On Mon, Apr 15, 2013 at 2:45 PM, Karl O. Pinc <ko...@me...> wrote: > On 04/14/2013 06:40:30 PM, Robert Treat wrote: > >> I'd like to get some independent confirmation that the packages look >> ok before I start sending announcements out to the world. Thanks in >> advance, > > bunzip2: /tmp/phpPgAdmin-5.1.tar.bz2: trailing garbage after EOF > ignored > > FWIW, I got the above when uncompressing. I suppose I could > have done something odd on download. > No, it appears to be something from building the release tarballs, but I haven't tracked it down to something specific. If I bunzip and bzip it back up, the problem seems to go away. AFAICT everything is fine in the package, but I plan to rewrap and release just in case. Robert Treat play: xzilla.net work: omniti.com |
From: Karl O. P. <ko...@me...> - 2013-04-15 18:45:14
|
On 04/14/2013 06:40:30 PM, Robert Treat wrote: > I'd like to get some independent confirmation that the packages look > ok before I start sending announcements out to the world. Thanks in > advance, bunzip2: /tmp/phpPgAdmin-5.1.tar.bz2: trailing garbage after EOF ignored FWIW, I got the above when uncompressing. I suppose I could have done something odd on download. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Robert T. <ro...@xz...> - 2013-04-15 16:48:08
|
On Mon, Apr 15, 2013 at 9:57 AM, Karl O. Pinc <ko...@me...> wrote: > On 04/15/2013 07:11:54 AM, Robert Treat wrote: >> On Sun, Apr 14, 2013 at 10:36 PM, Karl O. Pinc <ko...@me...> wrote: >> > On 04/14/2013 06:40:30 PM, Robert Treat wrote: >> > While I'm at it, what's with >> > http://git.postgresql.org/gitweb/?p=phppgadmin.git;a=summary >> > and how it compares to github? >> > >> >> Hmm, I bet it broke when we did the re-base a couple weeks back. I'll >> poke the pg folks about it. > > I don't know anything about it being broken. I wondered what it's role > in the universe is. > It's just a mirror of master. Robert Treat play: xzilla.net work: omniti.com |
From: Karl O. P. <ko...@me...> - 2013-04-15 13:57:43
|
On 04/15/2013 07:11:54 AM, Robert Treat wrote: > On Sun, Apr 14, 2013 at 10:36 PM, Karl O. Pinc <ko...@me...> wrote: > > On 04/14/2013 06:40:30 PM, Robert Treat wrote: > >> Howdy folks, > >> > >> 5.1 has been branched and tagged. > >> > >> The files are available on sourceforge at > >> https://sourceforge.net/projects/phppgadmin/files/phpPgAdmin%20% > >> 5Bstable%5D/phpPgAdmin-5.1/ > >> > >> I'd like to get some independent confirmation that the packages > look > >> ok before I start sending announcements out to the world. > > > > Is this the same as head? > > > > yes, except we rename the config file and remove the BUGS file IIRC. I'm going to mess with importable views, and probably insert/update/ delete on views today. I'll use the release files and see if anything bad happens. This won't be a comprehensive test.... I can't just install the release on my boxes since they're all patched. > > > While I'm at it, what's with > > http://git.postgresql.org/gitweb/?p=phppgadmin.git;a=summary > > and how it compares to github? > > > > Hmm, I bet it broke when we did the re-base a couple weeks back. I'll > poke the pg folks about it. I don't know anything about it being broken. I wondered what it's role in the universe is. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Robert T. <ro...@xz...> - 2013-04-15 12:12:01
|
On Sun, Apr 14, 2013 at 10:36 PM, Karl O. Pinc <ko...@me...> wrote: > On 04/14/2013 06:40:30 PM, Robert Treat wrote: >> Howdy folks, >> >> 5.1 has been branched and tagged. >> >> The files are available on sourceforge at >> https://sourceforge.net/projects/phppgadmin/files/phpPgAdmin%20% >> 5Bstable%5D/phpPgAdmin-5.1/ >> >> I'd like to get some independent confirmation that the packages look >> ok before I start sending announcements out to the world. > > Is this the same as head? > yes, except we rename the config file and remove the BUGS file IIRC. > While I'm at it, what's with > http://git.postgresql.org/gitweb/?p=phppgadmin.git;a=summary > and how it compares to github? > Hmm, I bet it broke when we did the re-base a couple weeks back. I'll poke the pg folks about it. Robert Treat play: xzilla.net work: omniti.com |
From: Karl O. P. <ko...@me...> - 2013-04-15 02:36:20
|
On 04/14/2013 06:40:30 PM, Robert Treat wrote: > Howdy folks, > > 5.1 has been branched and tagged. > > The files are available on sourceforge at > https://sourceforge.net/projects/phppgadmin/files/phpPgAdmin%20% > 5Bstable%5D/phpPgAdmin-5.1/ > > I'd like to get some independent confirmation that the packages look > ok before I start sending announcements out to the world. Is this the same as head? While I'm at it, what's with http://git.postgresql.org/gitweb/?p=phppgadmin.git;a=summary and how it compares to github? Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Robert T. <ro...@xz...> - 2013-04-14 23:40:38
|
Howdy folks, 5.1 has been branched and tagged. The files are available on sourceforge at https://sourceforge.net/projects/phppgadmin/files/phpPgAdmin%20%5Bstable%5D/phpPgAdmin-5.1/ I'd like to get some independent confirmation that the packages look ok before I start sending announcements out to the world. Thanks in advance, Robert Treat play: xzilla.net work: omniti.com |