On Wed, Jun 1, 2011 at 6:06 AM, Guillaume Lelarge
wrote:
> On Wed, 2011-06-01 at 01:05 +0200, Jasmin Dizdarevic wrote:
>> To better get into the code I've decided to implement a feature from
>> the todo list: "Ability to search a database for objects with a
>> specific name"
>> Now I have a first
On Wed, 2011-06-01 at 07:50 +, Dave Page wrote:
> On Wed, Jun 1, 2011 at 6:06 AM, Guillaume Lelarge
> wrote:
> > On Wed, 2011-06-01 at 01:05 +0200, Jasmin Dizdarevic wrote:
> >> To better get into the code I've decided to implement a feature from
> >> the todo list: "Ability to search a databa
On Wed, Jun 1, 2011 at 7:53 AM, Guillaume Lelarge
wrote:
>
> One is allowed to drop the information_schema system catalog? I didn't
> know that. I guess it's all right 'cause you don't really need it.
I'm surprised you didn't know that :-). pgAdmin doesn't let you drop
it because it disables drop
Can we use the pg_catalog?
2011/6/1 Dave Page
> On Wed, Jun 1, 2011 at 7:53 AM, Guillaume Lelarge
> wrote:
> >
> > One is allowed to drop the information_schema system catalog? I didn't
> > know that. I guess it's all right 'cause you don't really need it.
>
> I'm surprised you didn't know tha
On Wed, Jun 1, 2011 at 8:05 AM, Jasmin Dizdarevic
wrote:
> Can we use the pg_catalog?
Definitely - that's where we get all our info. I appreciate it's a
little more complicated; but it also exposes *all* Postgres object
types, unlike information_schema.
--
Dave Page
Blog: http://pgsnake.blogsp
On Wed, 2011-06-01 at 10:05 +0200, Jasmin Dizdarevic wrote:
> Can we use the pg_catalog?
>
pgAdmin works only by querying the PostgreSQL catalog.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.or
Alright, I'm going to change the query.
2011/6/1 Guillaume Lelarge
> On Wed, 2011-06-01 at 10:05 +0200, Jasmin Dizdarevic wrote:
> > Can we use the pg_catalog?
> >
>
> pgAdmin works only by querying the PostgreSQL catalog.
>
>
> --
> Guillaume
> http://blog.guillaume.lelarge.info
> http://www
Fix a number of synonym related issues:
- A crash when opening the new synonym dialog on PPAS 8.3r2.
- Labelling of the target type in the properties list.
- List only unique procedure/function names as possible targets.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgad
Fix a number of synonym related issues:
- A crash when opening the new synonym dialog on PPAS 8.3r2.
- Labelling of the target type in the properties list.
- List only unique procedure/function names as possible targets.
Branch
--
REL-1_12_0_PATCHES
Details
---
http://git.postgresql.org/g
Fix public synonym messages.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=5dc5b4d509da91bc8769ab9aa432c9330235864b
Modified Files
--
pgadmin/schema/pgObject.cpp |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
--
Sen
Only enable the Enable/Disable Trigger options if triggers actually
exist on the selected table. Also, fix a problem with constraint
trigger identification while we're at it.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=d5572bb6e29e06242632c2
Only enable the filter validation button if there's something to
validate.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=36c15214b59902fc825e56d6091282a46beec810
Modified Files
--
pgadmin/dlg/dlgEditGridOptions.cpp |9 ++
Only enable the filter validation button if there's something to
validate.
Branch
--
REL-1_12_0_PATCHES
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=24b0a971b1757f601cea14766559396c491ae9e7
Modified Files
--
pgadmin/dlg/dlgEditGridOptions.cpp
Hi, all here is my weekly report for second gsoc week.
a) what got done this week?
Last week I have been working in removing bad code, replacing code for a
more efficient version, finishing some old todo, fixing a lot of ugly
recursive bugs, and testing some ideas (I commit some and discard other
14 matches
Mail list logo
