> expect(column.toRow).toBe(9);
> })
> });
>
>
>
> Since we are finishing up this feature anyway, if this bug can wait
> another week, we can take it into our backlog and address it and submit the
> fix with our next patch.
>
>
> Thanks!
> Matt & Sara
May 5, 2017 at 5:54 AM, Murtuza Zabuawala <
[email protected]> wrote:
> Hi,
>
> PFA patch to fix the issue where in SlickGrid column resize also triggers
> 'onHeaderClick' event and triggers column selection, In this
> scenario before drag event which colu
Hi,
PFA patch to fix the issue where in SlickGrid column resize also triggers
'onHeaderClick' event and triggers column selection, In this
scenario before drag event which column is under mouse gets selected, So to
fix the issue we will check if header checkbox is clicked.
RM#2348
Ple
Add newly created triggers to the treeview. Fixes #1747
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=6e5126d571ca9497f90b25aa34f5f318a54b5089
Author: Murtuza Zabuawala
Modified Files
--
.../databases/schemas/tables/indexes
Properly format arguments passed by triggers to functions. Fixes #1912
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=c345adaa528571583a9e4df9c62785dfcbb5316d
Author: Murtuza Zabuawala
Modified Files
--
.../templates/trigger/sql
tions.
- Variables should be on their own tab, not the Security tab.
- There's no blank line before COMMENT ON in the Create script, or
before GRANT...
Triggers:
- The Definition tab on the Create dialogue needs to be split up. No
scrolling should be required!
- The Code tab should be hidde
Thanks - committed.
On Wed, Mar 23, 2016 at 3:43 PM, Surinder Kumar
wrote:
> Hi,
>
> Trigger and Rules nodes have functions which are also used by view node.
> View node use them while generating reverse engineering SQL for respective
> nodes.
> so they are moved into schema/utils.py
>
>
> Please
Hi,
Trigger and Rules nodes have functions which are also used by view node.
View node use them while generating reverse engineering SQL for respective
nodes.
so they are moved into schema/utils.py
Please review the patch.
Thanks,
Surinder Kumar
utility_functions_for_trigger_and_rule_node.pa
Default owner for new event triggers.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=fd05dec29c2e169ba9cb369902511fda8023b402
Modified Files
--
.../templates/event_triggers/js/event_trigger.js| 13 +
1 file
Add support for Event Triggers.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=986375d60e45f2e73c625342cc1a0fd024dece3e
Author: Harshal Dhumal
Modified Files
--
.../servers/databases/event_triggers/__init__.py | 664
Fix support for triggers with inline code on PPAS
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=97e21c673d762c583b06dd4194952a999b23983e
Author: Sanket Mehta
Modified Files
--
CHANGELOG|2 ++
pgadmin
Thanks, applied for 1.18.1+.
On Tue, Sep 24, 2013 at 10:39 AM, Dhiraj Chawla
wrote:
> Hi Dave,
>
> Please find the updated patch. I have moved the Event Triggers node before
> the Extensions node in the treeview. I have also re-arranged the the display
> options list to the best
> wrote:
> > Hi Dave,
> >
> > Please find the updated patch. I have moved the Event Triggers node
> before
> > the Extensions node in the treeview. I have also re-arranged the the
> display
> > options list to the best of my knowledge. Please review the patch
Hi Dave,
Please find the updated patch. I have moved the Event Triggers node before
the Extensions node in the treeview. I have also re-arranged the the
display options list to the best of my knowledge. Please review the patch
and let me know your thoughts on the same.
regards,
*Dhiraj Chawla
Hi
On Fri, Sep 20, 2013 at 1:13 PM, Dhiraj Chawla
wrote:
> Hi Dave,
>
> The Event Triggers options is not listed in the browser view options on the
> Settings dialog of pgAdmin, which would allow a user the hide/show the Event
> Triggers collection node. Attached is the patch
Hi Dave,
The Event Triggers options is not listed in the browser view options on the
Settings dialog of pgAdmin, which would allow a user the hide/show the
Event Triggers collection node. Attached is the patch that fixes this issue.
Let me know your view on the same.
regards,
*Dhiraj Chawla
Add support for event triggers in 9.3+.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=a71985564790c5dc3cbeb397d76c61f84a4ebc9a
Author: Dinesh Kumar
Modified Files
--
CHANGELOG |1 +
pgadmin/dlg
Fix constraint triggers SQL
Per a report from Michael Brux.
Branch
--
REL-1_14_0_PATCHES
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=0a77a3eeced2b7ced397fca82bf7d1e8646cfbea
Modified Files
--
CHANGELOG|1 +
pgadmin
Fix constraint triggers SQL
Per a report from Michael Brux.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=f9f1ae618462af01de0cd38163a97101bc9ac485
Modified Files
--
CHANGELOG|1 +
pgadmin/schema
Fix the SQL for existing triggers
Columns weren't quoted.
Per report from Bartosz Dmytrak.
Branch
--
REL-1_14_0_PATCHES
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=a62f04610bac5c9de8fffe6a478daabc90ad1b9e
Modified Files
--
CHAN
Fix the SQL for existing triggers
Columns weren't quoted.
Per report from Bartosz Dmytrak.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=086314a92c1a2a65c43d4c68f0c6539a932a1d07
Modified Files
--
CHAN
On Sat, 2011-07-09 at 10:18 +0100, Dave Page wrote:
> On Sat, Jul 9, 2011 at 10:12 AM, Guillaume Lelarge
> wrote:
> > Hi,
> >
> > Right now, the enabled/disabled state of a trigger and a rule is not
> > displayed in the SQL pane of the browser. I can understand we don't
> > display its state if th
Fix SQL query for enabled/disabled triggers and rules
When a user enables/disables a trigger, the icon changes, and the properties
are updated. But the SQL query in the query pane of the browser wasn't. Same
happens to enabled/disabled rules. This patch fixes both.
Branch
--
master
De
Fix SQL query for enabled/disabled triggers and rules
When a user enables/disables a trigger, the icon changes, and the properties
are updated. But the SQL query in the query pane of the browser wasn't. Same
happens to enabled/disabled rules. This patch fixes both.
Branch
-
On Sat, Jul 9, 2011 at 10:12 AM, Guillaume Lelarge
wrote:
> Hi,
>
> Right now, the enabled/disabled state of a trigger and a rule is not
> displayed in the SQL pane of the browser. I can understand we don't
> display its state if the object is enabled, but shouldn't we display
> that the object is
Hi,
Right now, the enabled/disabled state of a trigger and a rule is not
displayed in the SQL pane of the browser. I can understand we don't
display its state if the object is enabled, but shouldn't we display
that the object is disabled in the SQL pane if it is? Just like we show
a FK is invalid
gt;>>>>> I would like to suggest you a simple feature : is it possible to add,
>>>>>>>> in
>>>>>>>> the left panel of pgAdmin (objects browser), a visual feedback of
>>>>>>>> disabled triggers (like a red cross,
#306: Visual feedback of disabled triggers
--+-
Reporter: Erika| Owner: gleu
Type: feature | Status: closed
Priority: minor| Milestone: 1.14
Component: pgadmin
Disabled triggers are displayed with another icon
The "other" icon is the old one with a red cross on it. It helps to know which
triggers are enabled and which aren't.
Idea from Erika.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git
:
>>>>> On Tue, Feb 8, 2011 at 7:32 AM, Guillaume Lelarge
>>>>> wrote:
>>>>>> Le 04/02/2011 11:42, R.I.K a écrit :
>>>>>>> [...]
>>>>>>> I would like to suggest you a simple feature : is it possible to add,
gt;>> wrote:
>>>>> Le 04/02/2011 11:42, R.I.K a écrit :
>>>>>> [...]
>>>>>> I would like to suggest you a simple feature : is it possible to add, in
>>>>>> the left panel of pgAdmin (objects browser), a visual feedback of
>&
rit :
>>>>> [...]
>>>>> I would like to suggest you a simple feature : is it possible to add, in
>>>>> the left panel of pgAdmin (objects browser), a visual feedback of
>>>>> disabled triggers (like a red cross, for example, or a greyed icon)
t;>>> [...]
>>>>> I would like to suggest you a simple feature : is it possible to add, in
>>>>> the left panel of pgAdmin (objects browser), a visual feedback of
>>>>> disabled triggers (like a red cross, for example, or a greyed icon) ?
>&g
Le 06/03/2011 16:16, Peter Geoghegan a écrit :
> This is something we should have had a long time ago.
>
I guess so. Just needed to know about it and find the time to do it :)
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@
ple feature : is it possible to add, in
>>>> the left panel of pgAdmin (objects browser), a visual feedback of
>>>> disabled triggers (like a red cross, for example, or a greyed icon) ?
>>>>
>>>
>>> I think the greyed icon would be best. If we want
This is something we should have had a long time ago.
--
Regards,
Peter Geoghegan
--
Sent via pgadmin-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
#306: Visual feedback of disabled triggers
--+-
Reporter: Erika | Owner: gleu
Type: feature | Status: assigned
Priority: minor | Milestone:
Component: pgadmin
#306: Visual feedback of disabled triggers
--+-
Reporter: Erika | Owner: gleu
Type: feature | Status: assigned
Priority: minor | Milestone:
Component: pgadmin
in (objects browser), a visual feedback of
>>> disabled triggers (like a red cross, for example, or a greyed icon) ?
>>>
>>
>> I think the greyed icon would be best. If we want to do this, we need to
>> do this for rules too.
>
> We use a red cross for disco
#306: Visual feedback of disabled triggers
--+-
Reporter: Erika | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin
On Tue, Feb 8, 2011 at 7:32 AM, Guillaume Lelarge
wrote:
> Le 04/02/2011 11:42, R.I.K a écrit :
>> [...]
>> I would like to suggest you a simple feature : is it possible to add, in
>> the left panel of pgAdmin (objects browser), a visual feedback of
>> disabled trig
Le 04/02/2011 11:42, R.I.K a écrit :
> [...]
> I would like to suggest you a simple feature : is it possible to add, in
> the left panel of pgAdmin (objects browser), a visual feedback of
> disabled triggers (like a red cross, for example, or a greyed icon) ?
>
I think the greye
Hi,
I would like to suggest you a simple feature : is it possible to add, in
the left panel of pgAdmin (objects browser), a visual feedback of
disabled triggers (like a red cross, for example, or a greyed icon) ?
Thanks in advance,
--
Erika
--
Sent via pgadmin-hackers mailing list (pgadmin
#256: Add triggers on views support
--+-
Reporter: gleu | Owner: gleu
Type: feature | Status: closed
Priority: minor| Milestone: 1.14
Component: pgadmin | Version
Le 07/11/2010 06:40, Dave Page a écrit :
> On Thu, Nov 4, 2010 at 11:19 PM, Guillaume Lelarge
> wrote:
>> Some patience, yeah, I did use that :)
>>
>> New patch attached. Works good for me.
>
> Eyeball review looks OK.
>
Thanks, commited.
--
Guillaume
http://www.postgresql.fr
http://dalibo
On Thu, Nov 4, 2010 at 11:19 PM, Guillaume Lelarge
wrote:
> Some patience, yeah, I did use that :)
>
> New patch attached. Works good for me.
Eyeball review looks OK.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise P
cbFunction->GetValue() == wxString::Format(wxT("<%s>"), _("Inline EDB-SPL")))
sql += wxT("CREATE OR REPLACE TRIGGER ") + qtIdent(name);
else
sql += wxT("CREATE TRIGGER ") + qtIdent(name);
-if (rdbFires->Get
#256: Add triggers on views support
---+
Reporter: gleu | Owner: gleu
Type: feature| Status: assigned
Priority: minor | Milestone:
Component: pgadmin| Version
[Ashesh, if you haven't aready, I suggest reviewing this thread. It
may shed some light on that Rule weirdness on Solaris]
On Sat, Oct 23, 2010 at 11:03 PM, Guillaume Lelarge
wrote:
>> pgView derives from pgSchemaObject
>
> Actually, pgView derives from pgRuleObject, which is already weird by
> i
Le 23/10/2010 14:03, Dave Page a écrit :
> On Sat, Oct 23, 2010 at 3:00 PM, Guillaume Lelarge
> wrote:
>> Hi,
>>
>> It was much easier than I previously thought. This patch adds a Triggers
>> node in the each view object node if you're connected to a 9.1
>&g
On Sat, Oct 23, 2010 at 3:00 PM, Guillaume Lelarge
wrote:
> Hi,
>
> It was much easier than I previously thought. This patch adds a Triggers
> node in the each view object node if you're connected to a 9.1
> PostgreSQL server. You can add and see triggers on views.
>
Hi,
It was much easier than I previously thought. This patch adds a Triggers
node in the each view object node if you're connected to a 9.1
PostgreSQL server. You can add and see triggers on views.
It's not ready to be commited. I still have a bug to fix. I tried since
two days, and I
#256: Add triggers on views support
---+
Reporter: gleu | Owner: dpage
Type: feature| Status: new
Priority: minor | Milestone:
Component: pgadmin| Version: trunk
Fix the reverse-engineered query for triggers
The new "OF column" syntax is only available for UPDATE, and we should check
the args only if the number of args is not zero.
Set the bytea_output parameter to its old value on 9.0 right after a
connection. The tgargs column is of type
Fix the reverse-engineered query for triggers
The new "OF column" syntax is only available for UPDATE, and we should check
the args only if the number of args is not zero.
Set the bytea_output parameter to its old value on 9.0 right after a
connection. The tgargs column is of type
#97: Triggers on columns
--+-
Reporter: gleu | Owner: gleu
Type: feature | Status: closed
Priority: minor| Milestone: 1.12
Component: pgadmin | Version: trunk
#97: Triggers on columns
--+-
Reporter: gleu | Owner: gleu
Type: feature | Status: closed
Priority: minor| Milestone: 1.12
Component: pgadmin | Version: trunk
#97: Triggers on columns
--+-
Reporter: gleu | Owner: gleu
Type: feature | Status: closed
Priority: minor| Milestone:
Component: pgadmin | Version: trunk
#97: Triggers on columns
-+--
Reporter: gleu | Owner: gleu
Type: feature | Status: assigned
Priority: minor| Milestone:
Component: pgadmin | Version: trunk
#97: Triggers on columns
-+--
Reporter: gleu | Owner: dpage
Type: feature | Status: new
Priority: minor| Milestone:
Component: pgadmin | Version: trunk
#97: Triggers on columns
-+--
Reporter: gleu | Owner: dpage
Type: feature | Status: new
Priority: minor| Milestone:
Component: pgadmin | Version: trunk
Keywords: trigger
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 04 March 2002 22:24
> To: Dave Page; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Pseudo alter triggers
>
>
> Le Lundi 4 Mars 2002 21:33, Dave Page a écrit :
> > Bes
Le Lundi 4 Mars 2002 21:33, Dave Page a écrit :
> Best of both worlds I think, what about you?
This seems to be a nice solution my friend.
Cheers, Jean-Michel
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 04 March 2002 17:04
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-hackers] Pseudo alter triggers
>
>
> Dear all,
>
> I commited a fix to update display after pseudo-al
Dear all,
I commited a fix to update display after pseudo-altering triggers. Dave: this
might be ready for review...
Cheers,
Jean-Michel
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 22 February 2002 22:07
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Triggers
>
>
> Dear Dave,
>
> I commited a first implementation of pseudo ALTER TRIGGER to
Dear Dave,
I commited a first implementation of pseudo ALTER TRIGGER to CVS. Could you
please advice me on the following points:
1) How can I drop / add the trigger node after ALTER.
2) I don't know how to uncheck checkboxes in frmTrigger form.
These are very simple things to do...
Have a niv
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 20 February 2002 09:21
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Pseudo modification of views
> and triggers ( again)
>
>
> Le Mercredi 20 F
ur previous discussions? pgAdmin2 is
intended for a large audience, so better if no PL/pgSQL is required.
What I see in pgSchema is a powerfull pseudo "CREATE TABLE foo_new AS"
clause to copy schema information with selected linked objects (indexes,
columns, primary key, triggers, rules, etc
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 19 February 2002 21:19
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] Pseudo modification of views
> and triggers (again)
>
>
> > I've ju
t; NOTE: I also noticed that you do not retrieve the new OID. This could be
> done along with the definition.
Yes, you are right.
> Triggers could be implemented exactly as Views. Each property will need to
> be handled seperately, though in the future we might look into merging
> mul
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 19 February 2002 19:53
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Pseudo modification of views and triggers (again)
>
>
> Dear Dave,
>
> 1) Views
> View ps
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]]
> Sent: 19 February 2002 19:28
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-hackers] Pseudo modification of views and triggers
>
>
> Dear Dave,
>
> I implemented pseudo-modi
ews, but I may be wrong.
We need to rollback views in such a case.
Does this means implementing view modification at pgSchema->View level?
2) Triggers
It should be possible to change the name of a trigger as well as the
underlying function, but not the trigger table itself. Therefore, it
Dear Dave,
I implemented pseudo-modification of views based on the function example.
Pseudo modifiation is carried by a simple DROP /CREATE in both cases. This
was pretty easy : I just had to copy and adapt your code...
This seems to work fine. I will do the same for triggers and commit
OK, please disregard my last message!!!
Dear all,
I am using pgAdmin II on PostgreSQL 7.1.
It seems like triggers are not listed in server objects.
Do I miss something?
Best regards,
Jean-Michel POURE
77 matches
Mail list logo
