So long an thanks for all the fish!
How does the final release of pgadmin III v1.22.2 compare to the BigSQL
release "pgAdmin3 LTS 1.23.0a" A later version number, released earlier?
https://bigsql.com/components.jsp
https://bigsql.org/pgadmin3/index.jsp
Which one would you recommend as final vers
>>>
>>>>
>>>> Please let me know if I am right in my understanding or something is
>>>> missing.
>>>>
>>>>
>>>>
>>>> Regards,
>>>> Sanket Mehta
>>>> Sr Software engineer
>>
TABLES
TO bar;
Which is incorrect and misleading.
Regards
Erwin
On Thu, Aug 13, 2015 at 2:45 PM, Erwin Brandstetter
wrote:
> The display of ALTER DEFAULT PRIVILEGES statements can be incorrect.
>
> I reported this bug in 2013, but it seems like it never got through:
> http://www.po
The display of ALTER DEFAULT PRIVILEGES statements can be incorrect.
I reported this bug in 2013, but it seems like it never got through:
http://www.postgresql.org/message-id/528c2d00.6010...@falter.at
Details, with steps to reproduce:
https://redmine.postgresql.org/issues/694
Just tested with v
Hi developers!
The owner / target_role is missing from the SQL script for ALTER DEFAULT
PRIVILEGES.
Tested with pgAdmin 1.18.1 on Windows XP. Remote Postgres 9.1.10 Server
on Debian Linux.
But I assume this bug is affects all current versions.
== Steps to reproduce ==
As superuser postgres
On 11.08.2011 23:33, Guillaume Lelarge wrote:
On Wed, 2011-08-10 at 01:50 +0200, Erwin Brandstetter wrote:
On 10.01.2011 04:50, Erwin Brandstetter wrote:
On 06.01.2011 12:23, Guillaume Lelarge wrote:
Le 28/12/2010 20:18, Erwin Brandstetter a écrit :
(...)
Testing v.1.12.1 (Dec 13 2010, rev
On 10.01.2011 04:50, Erwin Brandstetter wrote:
On 06.01.2011 12:23, Guillaume Lelarge wrote:
Le 28/12/2010 20:18, Erwin Brandstetter a écrit :
(...)
Testing v.1.12.1 (Dec 13 2010, rev: REL-1_12_2) on Windows XP Pro, SP3
To be sure, I downloaded the latest version and upgraded. But there
have
On Feb 20, 11:51 pm, guilla...@lelarge.info (Guillaume Lelarge) wrote:
(...)
> If you are on the same network, just allow your computer to access the
> database server with the pg_hba.conf file.
>
> Otherwise, you can use an SSH tunnel.
Details to the above suggestion for internet connections (als
Hi!
I can't tell what triggered it for sure, but pgAdmin 1.12.2 would not start any
more on Windows XP Professional.
Maybe it was triggered by installing "Microsoft Visual C++ 2008
Redistributable".
Maybe it was triggered by uninstalling pgAdmin 1.10.2. (!).
We have had similar bug reports wit
On 06.01.2011 12:23, Guillaume Lelarge wrote:
Le 28/12/2010 20:18, Erwin Brandstetter a écrit :
On 28.12.2010 19:01, Guillaume Lelarge wrote:
Le 28/12/2010 18:41, Erwin Brandstetter a écrit :
On 29.10.2010 08:21, Guillaume Lelarge wrote:
Le 28/10/2010 00:33, Dave Page a écrit :
On Thu, Oct
On 06.01.2011 12:23, Guillaume Lelarge wrote:
Le 28/12/2010 20:18, Erwin Brandstetter a écrit :
(...)
Testing v.1.12.1 (Dec 13 2010, rev: REL-1_12_2) on Windows XP Pro, SP3
To be sure, I downloaded the latest version and upgraded. But there have
been no more changes in the meantime. Connection
On 28.12.2010 19:01, Guillaume Lelarge wrote:
Le 28/12/2010 18:41, Erwin Brandstetter a écrit :
On 29.10.2010 08:21, Guillaume Lelarge wrote:
Le 28/10/2010 00:33, Dave Page a écrit :
On Thu, Oct 28, 2010 at 5:25 AM, Guillaume Lelarge
wrote:
Dave, Magnus, any opinion on this?
It sure
On 29.10.2010 08:21, Guillaume Lelarge wrote:
Le 28/10/2010 00:33, Dave Page a écrit :
On Thu, Oct 28, 2010 at 5:25 AM, Guillaume Lelarge
wrote:
Dave, Magnus, any opinion on this?
It sure isn't a lot of code, and one can think it is a bugfix. Not
really my opinion, but I don't object to appl
On Oct 22, 8:45 pm, dp...@pgadmin.org (Dave Page) wrote:
> On Fri, Oct 22, 2010 at 7:42 PM, Josh Berkus wrote:
>
> >> Pretty darn hard actually. The lexer is part of wxWidgets, and is a
> >> generic SQL lexer. We have to write our own (probably clean-room
> >> style, because of the licencing). I w
<[EMAIL PROTECTED]>
To: Erwin Brandstetter <[EMAIL PROTECTED]>
References:
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
On Jun 4, 6:11 pm, Erwin Brandstetter <[EMAIL PROTECTED]> wrote:
Hi Kev!
On May 28, 2:27 pm, Kev <[EMAIL PROTECTED]> wrote:> Hi everyon
On Jun 16, 3:34 pm, [EMAIL PROTECTED] (Julius Tuskenis) wrote:
> Hi Laurent.
>
> As I understand where is no direct link between sequence and the table
> column. You should see pg_attrdef table.
> Query SELECT pg_get_expr(adbin,adrelid) FROM pg_attrdef; will return
> you all default values of the
Hi Simone!
On Jun 7, 9:28 am, [EMAIL PROTECTED] (Simone Gadenz) wrote:
> Hi all,
>
> this is the problem I am facing.
>
> I have PG 8.3 running on a KUBUNTU installation running on a virtual
> machine. From inside the virtual machine I can use PGADMIN to manage PG
> but when I try to connect from
Hi Brian!
Thanks for your report!
Please direct reports like that to the mailing-lists.
If you are merely helping the developers use this address:
[EMAIL PROTECTED]
For everything else, turn to:
pgadmin-support@postgresql.org
I took the liberty to cc [EMAIL PROTECTED]
Thanks & Regards
Michael Shapiro wrote:
I installed 1.8.4 and will use it. If there are problems, I'll let you
know. So far it looks OK.
On Wed, Jun 4, 2008 at 8:58 PM, Erwin Brandstetter
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Michael Shapiro wrote:
Erwin,
Michael Shapiro wrote:
The PgAdmin download page offers 1.8.4 -- even though the main page
says 1.8.2 is the current release.
Is 1.8.4 a good release? If not, is 1.8.3?
On Wed, Jun 4, 2008 at 5:11 PM, Erwin Brandstetter <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi Kev!
On May 28, 2:27 pm, Kev <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> I've had this problem maybe three times in the past few months and
> didn't think much of it, but since it happened again yesterday I
> thought I'd report it. Unfortunately I can't remember what I was
> doing at the tim
[EMAIL PROTECTED] wrote:
Fixed it is. Pleased you'll be.
Patience you shall need, master Dave!
Testing pgAdmin v.1.9.0-Dev (May 2 2008), rev: 7245:7266M, on WinXP;
host: pg 8.2.7 and 8.3.1 on Debian Etch.
The "Privileges" dialog seems fixed. But the reverse engineered SQL doesn't:
If I say:
On Apr 8, 3:01 pm, [EMAIL PROTECTED] ("Fernando Hevia") wrote:
(...)
> --- Function declaration follows in case it helps ---
> CREATE OR REPLACE FUNCTION f_inner(p_client numeric(10)) RETURNS void AS
> $BODY$
> DECLARE
> r_clients clientes%ROWTYPE;
> BEGIN
> SELECT * INTO r_clients FROM cliente
Dave Page wrote:
On Tue, Apr 1, 2008 at 1:17 AM, Erwin Brandstetter
<[EMAIL PROTECTED]> wrote:
Mistaken I am! A related, but different bug it is. This time, views it
affects, not tables.
Fixed it is. Pleased you'll be.
Pleased I shall be. May the force be with you,
I slightly miswrote:
I am afraid, the RULE privilege for pg >= 8.2 has risen from the dead
in pgadmin 1.8.2.
My original bug report (to pgadmin-support@postgresql.org at
2007-03-05) applies in full again.
Mistaken I am! A related, but different bug it is. This time, views it
affects, not tabl
Hi Dave!
Testing pgAdmin v.1.8.2 (Feb 5 2008), rev: 7050, on WinXP; host: pg 8.2.6 on
Debian Etch
I am afraid, the RULE privilege for pg >= 8.2 has risen from the dead in
pgadmin 1.8.2.
My original bug report (to pgadmin-support@postgresql.org at 2007-03-05)
applies in full again.
Regards
On Nov 16, 2:41 pm, [EMAIL PROTECTED] (Guillaume Lelarge) wrote:
> Which means we will have to support two branches, REL-1_8_0_PATCHES and
> trunk, till 7.4 is officially declared unsupported. If this is the case,
> I'm ok with this.
pgAdmin 1.8 will be there for older versions of pg, and it's no
Hi Mike!
On Oct 29, 5:30 pm, [EMAIL PROTECTED] wrote:
> A small annoyance: Newlines in table field comments appear to be stripped
> when the table is displayed in the Object Browser table list (upper right
> window). This makes multiline comments difficult to read. It'd be nice
> if the newline
Hi Mike!
On Oct 23, 7:00 pm, [EMAIL PROTECTED] wrote:
> Windows XP SP2
> pgAdmin dated 19 Oct 2007
> various 8.x.x versions of PostgreSQL
> ---
>
> The overloading of Ctl-V in the Edit window has been causing problems for
> me.
(...)
Try enabling the Option "Result Copy Quoting" for strings u
That's what I call a list!
If I wouldn't know better I'd say someone is trying to compensate for
certain shortcomings of his compatriots in other fields.
Like rugby. :)
/E
P.S.: I don't get any christmas cards anyway.
---(end of broadcast)---
TIP
Dave Page wrote:
Erwin Brandstetter wrote:
In a future release we could default to database "postgres" for global
objects, which is there for purposes like this one, isn't it?
It would be convenient to to open the SQL window directly from a role.
As long as we work on global obj
On Sep 15, 10:28 am, [EMAIL PROTECTED] (Dave Page) wrote:
> Rob McDonell wrote:
> > In both version 1.6 and 1.8 (can't remember earlier) the SQL button and
> > Query Tool menu item are inactive/greyed out when a Role is selected in
> > the Object Browser. This tool should always be available: regar
On Sep 17, 2:59 pm, [EMAIL PROTECTED] (Dave Page) wrote:
> Hmm, works for me in SVN-Trunk (1.8 beta5 + a few minor unrelated tweaks):
> (...)
> Anyone else able to reproduce this?
I cannot reproduce it either.
Testing pgAdmin III 1.8.0 Beta 5 (Sep 10 2007, rev: 6631). Client Win
XP, host: Debian
On Sep 15, 10:43 am, [EMAIL PROTECTED] (Dave Page) wrote:
> Harald Armin Massa wrote:
> > Hello,
>
> > it may or may not be considered as a pgadmin error:
>
> > I try to create an index on a column of a table. Using the
> > pgadmin-wizard, that results in:
>
> > CREATE INDEX otformularkopf_test
> >
Hi Harald!
On Sep 16, 8:56 pm, [EMAIL PROTECTED] ("Harald Armin Massa")
wrote:
> As much as I understood, pg_default is not necessarly the default
> tablespace??? But I never fiddled with tablespaces up to now :)
I have summed up which tablespace pg uses here:
http://archives.postgresql.org/pg
Hi Dave!
Congratulations, I think this one is very close to release. :)
> For details of the changes since v1.6, please see the changelog
> at:http://www.pgadmin.org/development/changelog.php
This may give a wrong impression, though. MUCH more has happened than
there is listed here.
Regards
Erwin Brandstetter wrote:
The tablespace issue concerns primary key - and unique constraints.
This should have gone into a separate paragraph but got mixed up.
I have had another look at this.
On Indexes, the field "Tablespace" is generally deactivated (with pg 8.1
or 8.2). I
Hi Dave!
Sounds like you've nailed issues with the big nail gun this morning. :)
Looking forward to the next version.
[EMAIL PROTECTED] wrote:
(...)
Erwin Brandstetter wrote:
The field "Tablespace" seems to do nothing at all. Choosing a
different tablespace does not
Erwin Brandstetter wrote:
- Trying to add a comment to UNIQUE CONSTRAINT fails altogether.
Actually, it doesn't fail to write. It just doesn't show up anywhere in
pgadmin afterwards.
psql doesn't seem to have a meta-command to retrieve comments on
constraints. But check
[EMAIL PROTECTED] wrote:
OK, I figured out how to hierarchically retain the expanded/collapsed
state of the child nodes during refresh - turned out to be *much* easier
that I thought it would be.
I've updated the .exe again - please let me know what you think.
Very good! But some things are
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
If any change via properties dialog would collapse the whole table
subtree that would be a change for the worse IMO. Then I'd rather have
the status quo ante.
Is there no way to just refresh the SQL pane?
Not really - it's
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
(...)
Concerning the issue at hand I am unsure what to look for. What Martin
addressed in his initial posting seems fixed in any case. Other things
might remain to be addressed.
For instance: add a new field per dialog.
-> field shows up
Hi Dave!
[EMAIL PROTECTED] wrote:
(...)
I've changed the behaviour somewhat so that's probably a little out of
date. There are undoubtedly some corner cases which would be a nightmare
to catch, but let's see if you pick anything up first.
I am back on my feet again and have run a few tests
Hi Dave!
[EMAIL PROTECTED] wrote:
(...)
Erwin; I'm somewhat wary of fixes in the treeview refresh code as there
can be odd corner cases caused by the relationships between some object
types. If I get you an updated exe, would you mind running it though
it's paces to help check I didn't miss
Hi Daniel!
On Aug 9, 1:01 pm, [EMAIL PROTECTED] ("Daniel Mendes")
wrote:
(...)
> I am using postgres installed in two different computers, in one I
> have to do the queries using quotation marks (select * from "Table")
> and in the other I can do select * from Table.
> What can I do to disable the
[EMAIL PROTECTED] wrote:
Dave Page wrote:
All is not necessarily lost however - it strike me that we might be able
to use the STC control instead of a rich textbox (thats the one we use
for the SQL input fields). I'll look into it
Unfortunately that doesn't seem to be feasible :-(
Dave Page wrote:
The problem is though, that it remains the underlying controls that
are doing the copy and the paste operations so we still have no way in
pgAdmin to filter it out. You can actually test this by pasting using
the button to do it - that does use our code which ensures it pastes
Sorry, I was in the process of editing my post, when the
groups.google.com decided to interpret " -" as my will to
send it. So the posting above is quite unfinished. §$%&/( interface! :
(
Anyway, here is what my finished posting would look like:
On Jul 19, 4:53 pm, [EMAIL PROTECTED] (Dave Page) wr
On Jul 19, 4:53 pm, [EMAIL PROTECTED] (Dave Page) wrote:
> Kieran McCusker wrote:
(...)
> > Copy and paste from edit grid adds a newline
> > ===
>
> > If you double click on a text field in the grid and do ctrl-c then paste
> > the result into another text field you get a ne
On Jun 22, 6:55 pm, [EMAIL PROTECTED] (Dave Page) wrote:
> A new snapshot of pgAdmin for windows is available
> fromhttp://developer.pgadmin.org/snapshots/win32/pgadmin3-20070622.msi
>
> Bug reports etc. to the normal places please :-)
I am away for a couple of days. Will run some tests next week
Hi developers! Hi Dave!
Testing pgAdmin III 1.7.0, rev 6292:6293. Client Win XP, hosts: Debian
Sarge / PG 8.1.8 and Debian Etch / PG 8.2.3
In the edit grid enter edit mode in a boolean field and hit . Now,
I know you wouldn't normally press that key in this particular
situation, but pgAdmin
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.3 rev: 6112, client Win XP, host: Debian Sarge,
PG 8.1.8.
Not sure, wheter this is any important.
While checking on the SQL sent to the database for displaying sequence
properties (with log_statement = 'all' in postgresql.conf) I made the
foll
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.3 rev: 6112, client Win XP, host: Debian Sarge,
PG 8.1.8.
A minor thing ..
In the dialogue window for the filter of the filtered table view, the
input field for the SQL filter has been shrunk in v1.6.3. As the
dialogue is otherwise empty, I se
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.3 rev: 6112, client Win XP, host: Debian Sarge,
PG 8.1.8.
It looks like an old bug has found its way back in. A snapshot from the
SQL query dialogue:
CREATE TABLE termin
(
beginn timestamp(0 without time zone,
...
)
Note t
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
(...)
Nice!
Additionally displaying the sequence's is_called flag in the properties
is not an easy option, I assume?
It's not a problem, it's just one of those things that inevitably leads
to confusion amo
[EMAIL PROTECTED] wrote:
(...)
I've implemented that change as suggested. The existing code went out of
it's way to behave as it did (using setval|('my_seq', 111, FALSE); on <
7.4 in fact!) so it was obviously a conscious design choice, but it's
not one I can see any justification for!
Cheers,
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.3 rev: 5941, client Win XP, host: Debian Sarge,
PG 8.1.8.
I have noted a peculiarity with seuqences.
If I change the "Current value" in the properties dialogue of a sequence
to a new value (111 in my example) pgAdmin sends this SQL statement t
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.2 rev: 5837, client Win XP, hosts: Debian
Sarge, PG 8.1.8 and Debian Etch, PG 8.2.3.
Testing pgAdmin III v1.6.3 rev: 5941, client Win XP, hosts: Debian
Sarge, PG 8.1.8 and Debian Etch, PG 8.2.3.
I have come across a peculiarity concerning the
tting in your postgresql.conf might be of interest.
BTW, backports.org has updated to postgresql 8.1.8 a couple of days ago.
You may want to apt-get update & upgrade ..
Regards
Erwin
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
[EMAIL PROTECTED] wrote:
I am interested to know if
Hi Dave!
[EMAIL PROTECTED] wrote:
Yes. We don't display the extra detail there because for non-fixed width
fonts the marker ends up in the wrong place. What we do instead is
display a marker in the left margin of the SQL pane to show the line
where the error occurred, and bung a squiggly underli
le to reproduce this error: it seems its due to my PG
server configuration (Ubuntu with French locale), other configurations
(including on WinXP machine) work fine.
- Message d'origine ----
De : Erwin Brandstetter <[EMAIL PROTECTED]>
À : pgadmin-support@postgresql.org
Envoyé le : Me
Hi Dave!
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
(...)
The "essential" part ist the "%" at the end of the first string.
Yeah, in some cases that string was going through a printf variant, so
it was trying to expand the %. Fixed for 1.6.3.
After th
Regards
Erwin
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
(...)
...
The "essential" part ist the "%" at the end of the first string.
Yeah, in some cases that string was going through a printf variant, so
it was trying to expand the %. Fixed for 1.6.3.
igurations
(including on WinXP machine) work fine.
Cheers,
[EMAIL PROTECTED]
The Computing Froggy
- Message d'origine
De : Erwin Brandstetter <[EMAIL PROTECTED]>
À : pgadmin-support@postgresql.org
Envoyé le : Mercredi, 21 Février 2007, 2h06mn 21s
Objet : [pgadmin-support] Cra
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.2 rev: 5837, client Win XP, host Debian Sarge,
PG 8.1.4. / Debian Etch, PG 8.2.1.
I have found a 'reliable' way to crash pgAdmin. Look at the following query:
select * from loc where loc like 'a%' loc = 'b';
Note the syntax error: "and" is
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.2 rev: 5837, client Win XP. Host Debian Sarge,
PG 8.1.4.
While having a look at the new release, I think I found an issue with
truncated column comments. It seemed quite random at first, I guess I
have figured it out, though:
If the comment
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
Maybe this happens on purpose to shorten lengthy comments.
It does.
But then again, a better way would probably be to print the first x
(200?) characters (substituting spaces for linebreaks) and append '
...' if there is more.
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.1 rev: 5709, client Win XP. Host Debian Sarge,
PG 8.1.4.
The data types "timestamp" and "time" (with or without time zone) with
precision modifiers are displayed incorrectly.
Notably, the data type interval seems not to be affected.
I have cre
Hi developers! Hi Dave!
Using pgAdmin III v1.6.1 rev: 5709, client Win XP. Host Debian Sarge, PG
8.1.4.
In the object browser comments are appended to the columns of a table
definition, which is useful.
But it looks like those comments are cut off after the first line break.
Simple test case
[EMAIL PROTECTED] wrote:
Were you doing that over a vpn connection by chance?
(...)
Hi Mike!
No, this time I have been working via plain TCP/IP to port 5433 in the
company intranet.
From outside the company I usually connect via SSH-tunnel and port
forwarding, which works just as well. I
Hi developers! Hi Dave!
Testing 1.6.1 rev: 5709, client Win XP. Host Debian Sarge, PG 8.1.4
A new version is out. Congratulations on your good work! :)
I have run a few tests, found nothing bad, and used it for serious work.
Found something bad though, when I was not looking. Here is what I did
Dave Page wrote:
Milen A. Radev wrote:
I consider the decision to distinguish between functions and procedures
in pgAdmin's UI very unfortunate.
(..)
I'm happy to discuss re-engineering that if people want (can't guarantee
I'll actually get time to change anything myself though).
As I have
Hi developers! Hi Dave!
Testing 1.6.1 rev: 5646:5664M, client Win XP. Host Debian Sarge, PG 8.1.4
I noticed that primary key and unique constraints (both create an index)
are listed twice in the object tree, under "Indexes" and "Constraints".
In 1.4.3 those were only listed under "Constraints".
Hi Dave!
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
BTW: what exactly makes a procedure a procedure and not a function?
OUT-parameters, right?
Yes - and we don't recommend use of return values from a procedure.
To clarify: "we" stands for the PostgreSQL develop
Hi developers! Hi Dave!
After the release is before the release, huh? :)
Testing 1.6.1 rev: 5646:5652M, client Win XP. Host Debian Sarge, PG 8.1.4
- Cancel in "View Data Options" now works as expected. I have seen no
more crashes.
- Find and Replace
Replacing now works as expected, I think
Di Dave!
Testing 1.6.0 rev: 5641
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
# One more cornercase for "Find and Replace". Try to replace multiple
occurrences of 'abc' with 'abcd' and see for yourself ..
Seems like "Replace" continues the
Downloaded pending 1.6.0 rev: 5641
Deinstalled v1.6 RC2, restarted PC, installed pending release 1.6.0 rev:
5641.
Crash is still reproducible.
Regards
Erwin
[EMAIL PROTECTED] wrote:
Hi developers! Hi Dave!
Testing 1.6RC2 rev: 5636M, client Win XP.
I am afraid I have discovered a grave bug.
Hi developers! Hi Dave!
Testing 1.6RC2 rev: 5636M, client Win XP.
I am afraid I have discovered a grave bug.
When I try to open a table via the filter-dialogue (button: grid with
funnel) and click Cancel in the "View Data Options" dialogue, pgAdmin
crashes. I have tried this a couple of times
Hi developers! Hi Dave!
Testing 1.6RC2 rev: 5636M, client Win XP.
# One more cornercase for "Find and Replace". Try to replace multiple
occurrences of 'abc' with 'abcd' and see for yourself ..
Seems like "Replace" continues the search at the _beginning_ of the
newly inserted text. If the sear
f the mail.
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
- Starting new lines by inserting data is now less confusing, the new
dialogue prevents data loss. And the option to cancel the operation
is a major improvement. That's the one I will be using 99% of the time.
The current way of
Hi developers! Hi Dave!
[EMAIL PROTECTED] wrote:
- While experimenting with pasting, I pasted the dummy text 'asdfg' to
an integer column and saved - which produced an error as expected. The
nature of the error was a bit of a surprise though:
An error has occurred:
FEHLER: Spalte >>asdf
[EMAIL PROTECTED] wrote:
- The undead "undo" issue:
The save dialogue pops up, even if there is no data to save, even if I
did not enter edit mode in the row of the cursor at all, ...
To clarify: the new save dialogue when pasting a new row by pressing
while not in edit mode.
/Erwin
---
Hi developers! Hi Dave!
Dave, I have tested the new version you sent me. RC2, rev: 5607:5627M.
(5627M?)
- No crashes or anything major sighted in two hours of testing (mainly
edit grid).
- You have definitely improved the handling of timestamps, dates and
intervals. Copy & paste is much more
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
[EMAIL PROTECTED] wrote:
And in case you were wondering, we use the wxTE_RICH flag to allow
the control to hold more than 64KB of text (though I do wonder if
that's actually still required).
Now that you have disabled editing byte
[EMAIL PROTECTED] wrote:
It actually seems to happen on paste, not copy, and happens with the
editor in rich text mode. It's a wx bug though so I'll log it with them.
As you can deselect the ghost linebreak before copying, and if you do,
it won't be pasted, it certainly looks like it owuld h
Hi developers! Hi Dave!
Testing RC2, rev 5607:5610. Client Win XP.
There is one more longstanding issue I have not reported yet and can't
find in the "known issues" list.
In edit mode, you can select an extra linebreak past the last real
character. You cannot navigate the cursor past the las
Hi developers! Hi Dave!
Testing RC2, rev 5607:5610. Client Win XP, Server Debian Sarge,
PostgreSQL 8.1.4.
In the SQL dialogue window, if a view has a long line of code the
vertical scrollbar will get it wrong.
Trying to scroll to the right end ends halfway into the line.
Same thing in the S
Hi Dave!
[EMAIL PROTECTED] wrote:
Thanks for the insight.
So, onto the changes I've made:
1) When a new row paste occurs, the cursor cell is moved to the
position of each column as data is inserted, such that it will be on
the last affected cell when the paste has completed. This ensure
Hi developers! Hi Dave!
Testing RC2. Client Win XP, Server Debian Sarge, PostgreSQL 8.1.4.
I think I have found more issues in the edit grid, which have some
potential to damage things.
Sorry to bring this up so close to release. I did not find it any
earlier. Anyway, it is up to you what you
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
(...)
If I hit now, I end up with FALSE (!). That wouldn't be by
design, would it?
Probably not :-). I've committed a change which modifies the behaviour
such that simply clicking on the cell no longer cycles the value - it
Ezequias Rodrigues da Rocha wrote:
Hi list,
Could someone suggest me how to get a documentation about Groups and
Roles and Users ?
It would be nice to see a simple and easy documentation (a tutorial
could be better, with pgadmin much better).
Hi Ezequias!
Try the docs for a start:
www.pos
Hi developers! Hi Dave!
Testing RC1. Client is Win XP. Server is Debian Sarge.
I have come across a peculiar effect while editing boolean fields. With
other fields, if you want to discard your changes while editing a field,
you hit and the original value is back (as long as you haven't
saved
Hi Dave!
I am afraid I have encountered another one of those undead bugs.
It would seem that the case where the return type of a function is
specified via OUT-parameter has slipped through:
That's what I get for one of my real functions (note the duplicated
schema-name with the OUT-parameter!):
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
Hi developers! Hi Dave!
Testing bet4, rev. 5567:5572 on Win XP
I found a couple of quirks in the edit grid.
- If I mark part of the text in a field and press only first
character of the marked text gets deleted. One would expect all of
the
novnov wrote:
Is there anything like SOP for pgsql devs then? Do most stick to lowercase
everywhere, and skip the issues, or do they keep the namestyles like
"ItemName" and just accomodate the need to double quote when it arises? I am
sure good devs could go either way, but curious if you or othe
Dave Page wrote:
Erwin Brandstetter wrote:
I can reproduce that in beta4.
Reproduce what?
*Was meant to be a reply to Raymond O'Donnell´s mail from 10/29. Tried
to send via news server of my provider, but it sucks and took a few days
to arrive.
You have answered Raymond already, so i
I have checked out v1.6 RC1 and both issues are still there.
Regards
Erwin
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
matc
[EMAIL PROTECTED] wrote:
Trying to find strings starting with ' ' (space) generally fails.
I found that the alleged issue with the leading space was due to the
option "Whole word" being checked.
However, there are other, more severe issues:
- Replacing ceases to work after non-latin-1 (or at
Hi developers! Hi Dave!
Still testing beta4, rev. 5567:5572 on Win XP.
Trying to find strings starting with ' ' (space) generally fails.
Regards
Erwin
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.p
I can reproduce that in beta4.
Regards
Erwin
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
1 - 100 of 133 matches
Mail list logo
