something alpha.
At worst it means the new version is incompatible with the prior version, which
is a completely separate issue save where the incompatibility is due to a bug
rather than an intentional omission.
-- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@post
sometimes taking things away is beneficial. That's
not to say that taking some things away isn't painful, but that's not the case
with all features and options.
-- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to yo
.
-- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
Considering that Postgres 9.2 itself is still officially supported for another
year, I wouldn't expect pgAdmin 4 to not support it. -- Darren Duncan
On 2016-10-28 3:46 AM, André Cardoso wrote:
Too "old" PostgreSQL version (9.2)?
Keep using PgAdmin3...
2016-10-28 8:42 GMT-0
. -- Darren Duncan
On 2016-10-27 4:29 AM, Dave Page wrote:
The pgAdmin Development Team are pleased to announce the release of
pgAdmin 4 v1.1. This is the second release of pgAdmin 4, and includes
over 40 bug fixes and improvements. For details, please see the issue
tracker roadmap:
https
next year? From an ease of use
perspective, it would be great for users if the tunneling didn't take too
terribly long to become available. Thank you. -- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your sub
ecurity of compatibility
or bug fixes but not major features. It would probably only get major
enhancements if someone wants them enough to pay to have them developed or do it
themselves. But downloading should work for a long time. -- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadm
would present a larger attack surface on the DBMS from the public. I
wouldn't want to allow connections to Postgres directly from the public internet
either. -- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
that normally field order shouldn't matter, and in the relational model
fields aren't ordered, but in SQL they are significant.
-- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
levant C header files which you otherwise don't have. -- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
later on, when you were *using*
the table you had already created, per your examples.
-- Darren Duncan
On 2014-06-02, 5:43 AM, Rob Richardson wrote:
Darren,
You are not listening to me.
If I was using plain SQL, entered manually, I would use all lower-case
characters.
I am not using plai
.
See, SQL entities are case-sensitive in the general case of being quoted, but in
the special case of not quoting the names in SQL, they are folded to lowercase
before being matched.
If this is all complicated to you, then just use straight lowercase everywhere
and it will just work.
-- Darren
re in your query; such as that is what lets you do this query
without having to write procedural code or a query that only works for a
specific number of levels. -- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
John, I believe that in Postgres-land, the term 'pgdata' has a fairly standard
meaning which lets you tell the program where your database directory is if it
isn't in a standard location, that might be part of it. -- Darren Duncan
On 1/16/2014, 9:18 AM, Sebastian, John (CONTR) w
again most likely.
In similar fashion, I would anticipate a 9.3.1 release about 2 weeks later,
around the last week of September, also following 9.2/9.1 precedent. And 9.3.2
in December unless there's something so critical it needs to go sooner.
-- Darren Duncan
--
Sent via pgadmin-suppo
al programs are
capable of opening a particular file, its not like the operating system can read
your mind as to which one you want to use, you have to tell it, otherwise it
will just pick any one of them (which sometimes is okay). -- Darren Duncan
--
Sent via pgadmin-support mailing list
do to help resolve this?
-- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
pgAdmin is the minimal request.
Thank you.
-- Darren Duncan
05.04.2013 21:31 пользователь "Darren Duncan" написал:
I have a feature request for pgAdmin that would help me and other users a
lot, and I don't see it on your roadmap or TODO.
This is to add to Server R
ank you in advance.
-- Darren Duncan
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
Maybe "pgScript" is something special.
Normally I execute my multi-statement SQL script files using the "Execute Query"
plain green arrow, which works fine.
I recalled that when I tried the "Execute pgScript" button using the exact same
SQL, it gave errors.
20 matches
Mail list logo
