On Sat, Jun 11, 2011 at 1:37 PM, Guillaume Lelarge
wrote:
> On Sat, 2011-06-11 at 11:22 +0200, Guillaume Lelarge wrote:
>> On Fri, 2011-06-03 at 14:24 +0100, Dave Page wrote:
>> > On Fri, Jun 3, 2011 at 1:45 PM, Guillaume Lelarge
>> > wrote:
>> > >
>> > > Hi,
>> > >
>> > > On Thu, 2011-06-02 at 0
On Mon, 2011-06-13 at 10:18 +0100, Dave Page wrote:
> On Sat, Jun 11, 2011 at 1:37 PM, Guillaume Lelarge
> wrote:
> > On Sat, 2011-06-11 at 11:22 +0200, Guillaume Lelarge wrote:
> >> On Fri, 2011-06-03 at 14:24 +0100, Dave Page wrote:
> >> > On Fri, Jun 3, 2011 at 1:45 PM, Guillaume Lelarge
> >> >
Fix our i18n support.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=6f88f423f024d9ed5d6081c66f2351249a5bd190
Modified Files
--
pgadmin/agent/pgaJob.cpp | 55 +++--
pgadmin/agent/pgaSchedule.cpp
Forgot to increment the perspective number
I should have done this with commit c49f3bdbf097577bc8955f47eb19ceb991351ddf.
Per a report from Erwin Brandstetter.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=8647abd390612c590dc1f2f6f51c7c68f076
On Mon, 2011-06-13 at 00:36 +0200, Erwin Brandstetter wrote:
> On 12.06.2011 08:59, Guillaume Lelarge wrote:
> > On Sat, 2011-06-11 at 22:24 +0200, Erwin Brandstetter wrote:
> >> On 11.06.2011 18:16, Guillaume Lelarge wrote:
> >>> On Sat, 2011-06-11 at 18:13 +0200, Erwin Brandstetter wrote:
>
Automatic merge using stringmerge script.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=7ebf4c02d962436c00c872b714a4f50bdfc01c7c
Modified Files
--
i18n/af_ZA/pgadmin3.po | 4229 ++---
i18n/ar_SA/pgadmin3.po | 4334 ++---
i18
Update .pot file.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=6f5150b3b909c39e1c712f5e1f5602f17ba69b75
Modified Files
--
pgadmin3.pot | 3582 --
1 files changed, 2224 insert
On 13.06.2011 14:56, Guillaume Lelarge wrote:
On Mon, 2011-06-13 at 00:36 +0200, Erwin Brandstetter wrote:
On 12.06.2011 08:59, Guillaume Lelarge wrote:
On Sat, 2011-06-11 at 22:24 +0200, Erwin Brandstetter wrote:
(...)
After closing pgAdmin a new entry "perspective-8316" landed in the
regi
On Mon, Jun 13, 2011 at 1:50 PM, Guillaume Lelarge
wrote:
> On Mon, 2011-06-13 at 10:18 +0100, Dave Page wrote:
>> On Sat, Jun 11, 2011 at 1:37 PM, Guillaume Lelarge
>> wrote:
>> > On Sat, 2011-06-11 at 11:22 +0200, Guillaume Lelarge wrote:
>> >> On Fri, 2011-06-03 at 14:24 +0100, Dave Page wrote
Hi
On Wed, Jun 8, 2011 at 5:22 PM, Dave Page wrote:
> [please remember to CC the list - even when pointing out that I'm
> suffering from brain failure :-) ]
>
> On Wed, Jun 8, 2011 at 10:56 AM, Akshay Joshi
> wrote:
> > Hi
> >
> > On Wed, Jun 8, 2011 at 3:06 PM, Dave Page wrote:
> >>
> >> On W
On Mon, 2011-06-13 at 15:13 +0200, Erwin Brandstetter wrote:
> On 13.06.2011 14:56, Guillaume Lelarge wrote:
> > On Mon, 2011-06-13 at 00:36 +0200, Erwin Brandstetter wrote:
> >> On 12.06.2011 08:59, Guillaume Lelarge wrote:
> >>> On Sat, 2011-06-11 at 22:24 +0200, Erwin Brandstetter wrote:
> >>>
>
Hi
Sorry by mistaken attached the old screenshot in the previous mail.
Reattaching the new screenshot.
On Mon, Jun 13, 2011 at 7:26 PM, Akshay Joshi wrote:
> Hi
>
> On Wed, Jun 8, 2011 at 5:22 PM, Dave Page wrote:
>
>> [please remember to CC the list - even when pointing out that I'm
>> suffer
Thanks!
On Mon, Jun 13, 2011 at 2:59 PM, Akshay Joshi
wrote:
> Hi
> Sorry by mistaken attached the old screenshot in the previous mail.
> Reattaching the new screenshot.
>
> On Mon, Jun 13, 2011 at 7:26 PM, Akshay Joshi
> wrote:
>>
>> Hi
>>
>> On Wed, Jun 8, 2011 at 5:22 PM, Dave Page wrote:
>>
Update the slony upgrade screenshot.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=656222626a988c95ff1664c452ede811aaead843
Author: Akshay Joshi
Modified Files
--
docs/en_US/images/slony-upgrade.png | Bin 13400 -> 13961 bytes
1
Greetings,
Interesting inconsistency in the cut / paste operation in pgAdmin. I
am using 1.14.0 beta 2.
If you View the top 100 rows you get a spreadsheet like display
showing the rows. If you then select a row (not its data) and copy
it. You then paste it (to the scratch pad buffer below for
Greetings,
I also found that if you cut / paste multiple columns, the columns get
separated with semi-colons. For SQL it would be much better to use
commas.
Thanks.
Blake McBride
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
ht
On Mon, 2011-06-13 at 15:39 -0500, Blake McBride wrote:
> Greetings,
>
> Interesting inconsistency in the cut / paste operation in pgAdmin. I
> am using 1.14.0 beta 2.
>
> If you View the top 100 rows you get a spreadsheet like display
> showing the rows. If you then select a row (not its data)
On Mon, 2011-06-13 at 15:49 -0500, Blake McBride wrote:
> Greetings,
>
> I also found that if you cut / paste multiple columns, the columns get
> separated with semi-colons. For SQL it would be much better to use
> commas.
>
Same reason. You can change it in the options dialog (tab "Query tool"
On Tue, 2011-06-14 at 00:29 +0200, Guillaume Lelarge wrote:
> On Mon, 2011-06-13 at 15:39 -0500, Blake McBride wrote:
> > Greetings,
> >
> > Interesting inconsistency in the cut / paste operation in pgAdmin. I
> > am using 1.14.0 beta 2.
> >
> > If you View the top 100 rows you get a spreadsheet
On Monday, June 13, 2011, Guillaume Lelarge wrote:
> On Mon, 2011-06-13 at 15:39 -0500, Blake McBride wrote:
>> Greetings,
>>
>> Interesting inconsistency in the cut / paste operation in pgAdmin. I
>> am using 1.14.0 beta 2.
>>
>> If you View the top 100 rows you get a spreadsheet like display
>>
In a relationship between tables, I need to allow use of existing columns as
destination target of my foreign key columns.
Right now, when a user create a relationship between two tables, he should
select kind: from fk or from uk ( and which?) and the fk columns are created
in an automatic way at d
21 matches
Mail list logo
