Fix freeze of UI when querytool has an error on a query
We call too many times the GetCharAt() and the GetText().Length() methods.
This fix calls GetCharAt() once per loop (instead of five times per loop), and
GetText().Length() once only (instead of once per loop). My testing shows no
freeze at a
Fix freeze of UI when querytool has an error on a query
We call too many times the GetCharAt() and the GetText().Length() methods.
This fix calls GetCharAt() once per loop (instead of five times per loop), and
GetText().Length() once only (instead of once per loop). My testing shows no
freeze at a
#369: Edit data and tables with a unique key
--+-
Reporter: gleu | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: trunk
#370: pgScript error when relation name contains ")" symbol
--+-
Reporter: Vjacheslav A | Owner: dpage
Type: bug | Status: new
Priority: minor | Milestone:
Component: pgadmi
On Fri, 2012-07-13 at 21:47 -0300, Vinicius Santos wrote:
> > So, this information would solve the problem. What do you think?
> >
>
> Any comment? Can I develop the patch?
You can certainly work on a patch. Shouldn't be hard to code.
I see some value on it, but I don't like the arrow.
--
Gui
On Fri, 2012-07-13 at 09:32 +0100, Dave Page wrote:
> On Fri, Jul 13, 2012 at 7:57 AM, Akshay Joshi
> wrote:
> >
> >
> > On Thu, Jul 12, 2012 at 5:44 PM, Magnus Hagander
> > wrote:
> >>
> >> On Thu, Jul 12, 2012 at 2:06 PM, Akshay Joshi
> >> wrote:
> >> >
> >> >
> >> > On Thu, Jul 12, 2012 at 5:
Forwarding, sorry.
2012/7/14 Vinicius Santos
> I see some value on it, but I don't like the arrow.
>>
>
> Any suggestions?
> I could put the point rather than the arrow or other something. What do
> you think?
>
On Sat, 2012-07-14 at 10:59 -0300, Vinicius Santos wrote:
> Forwarding, sorry.
>
> 2012/7/14 Vinicius Santos
> I see some value on it, but I don't like the arrow.
>
>
> Any suggestions?
> I could put the point rather than the arrow or other
>
> Not sure I like the point either. We don't have that notation on
> PostgreSQL. I think I would prefer something like "Retrieving details on
> table schema.table" and not say the database. Because if you add the
> database, someone will probably want also the server. It may not be
> usefull to you
On Sat, 2012-07-14 at 11:28 -0300, Vinicius Santos wrote:
>
> Not sure I like the point either. We don't have that notation
> on
> PostgreSQL. I think I would prefer something like "Retrieving
> details on
> table schema.table" and not say the database. Beca
>
> I think I like the second one better, but this is just my opinion.
>
Well, I'll start working on the second, then.
If new opinions, we changed.
On Saturday, July 14, 2012, Guillaume Lelarge wrote:
> On Sat, 2012-07-14 at 11:28 -0300, Vinicius Santos wrote:
> >
> > Not sure I like the point either. We don't have that notation
> > on
> > PostgreSQL. I think I would prefer something like "Retrieving
> > detail
On Sat, 2012-07-14 at 18:57 +0100, Dave Page wrote:
>
>
> On Saturday, July 14, 2012, Guillaume Lelarge wrote:
> On Sat, 2012-07-14 at 11:28 -0300, Vinicius Santos wrote:
> >
> > Not sure I like the point either. We don't have that
> notation
> >
On Saturday, July 14, 2012, Guillaume Lelarge wrote:
> On Sat, 2012-07-14 at 18:57 +0100, Dave Page wrote:
> >
> >
> > On Saturday, July 14, 2012, Guillaume Lelarge wrote:
> > On Sat, 2012-07-14 at 11:28 -0300, Vinicius Santos wrote:
> > >
> > > Not sure I like the
14 matches
Mail list logo
