pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedpgAdmin v6.4.2
6+ messages / 2 participants
[nested] [flat]
* pgAdmin v6.4.2
@ 1999-02-11 16:06 Dave Page <dpage@vale-housing.co.uk>
0 siblings, 0 replies; 6+ messages in thread
From: Dave Page @ 1999-02-11 16:06 UTC (permalink / raw)
To: pgsql-interfaces
I've just released pgAdmin v6.4.2 which is available from:
http://www.vale-it.demon.co.uk/freeware
New features/enhancements include:
1) Improved the error logging to include details of the database connection
and some internal variables in the logfile.
2) Added a check to prevent use with earlier versions of PostgreSQL than
are compatible.
3) Added checks to warn the user if the ODBC driver settings for the
datasource could cause problems with the operation of pgAdmin.
4) Added a Database browser dialogue with Create and Drop database
facilities.
Please note that pgAdmin 6.4.x will only work correctly with PostgreSQL
6.4.x.
Regards,
Dave.
--
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] pgAdmin v6.4.2
@ 1999-02-12 08:32 Dave Page <dpage@vale-housing.co.uk>
1999-02-12 15:12 ` Re: [INTERFACES] pgAdmin v6.4.2 David Hartwig <daveh@insightdist.com>
0 siblings, 1 reply; 6+ messages in thread
From: Dave Page @ 1999-02-12 08:32 UTC (permalink / raw)
To: 'David Hartwig' <daveh@insightdist.com>; +Cc: pgsql-interfaces
Hi David,
> -----Original Message-----
> From: David Hartwig [mailto:daveh@insightdist.com]
> Sent: 11 February 1999 20:04
> To: Dave Page
> Subject: Re: [INTERFACES] pgAdmin v6.4.2
>
>
> Nice app!
Thanks. We aim to please!
> However, there is one item that you may want to address.
> While browsing
> through the Schema Tables, if I click on a column name I
> often get an error.
> "Error 3021, No current record." Perhaps I am doing
> something incorrect.
> The message only occurs when there in NO default value for
> the column. I
> inspected the ODBC driver CommLog and observed that, in
> fact, pgadmin was
> querying for these default values and was returning an empty
> record sets.
> This does not seem as if it should be considered an error condition.
I'll look into this. I can't seem to reproduce it though, so if you could
send me your CommLog and the c:\pgerr.log file it would be a help.
> If you ever get bored and are looking for something to do,
> here are some ideas.
I always looking to improve pgAdmin. The main constraint seems to be all
this other work my employee seems to (somewhat unreasonably I think!) want
finished.
> 1. Implement a function and trigger management tool.
> (I've been really
> getting into this stuff lately.)
> o Display all the triggers under each table and
> which events they
> respond to.
> o Allow create/drop of triggers.
> o Allow create/drop/edit of function - provide
> simple editor
> modify the text of plpgsql code.
This and other things are on the ToDo list at the moment. The problem is
that having never used triggers or functions etc. on any dbms at all, there
is a bit of a learning curve - both in figuring out how the work, and then
in getting the infomation on them from the relevant system tables.
I'll get there eventually...
> o Allow the user to document the functions and
> triggers - you
> would probably have to add one ore more helper tables to
> maintain this info.
>
> 2. Provide a mechanism much like the last item above to
> document tables
> and columns.
I like this idea - and it shouldn't be too difficult to implement quite
quickly.
> I could see a tool like this as being very useful in building
> and managing a
> schema from the ground up. Nice work.
Thanks. Thats the intention of the program. It's initial design came about
when I started working on some client server apps in VB and decided I was
fed up with modifying the schema via a telnet session!
> Oh, if I sound like I am being a bit liberal with the use of
> YOUR time, my
> apologies.
No problem, I need kicking occasionally!
Regards,
Dave.
--
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [INTERFACES] pgAdmin v6.4.2
1999-02-12 08:32 RE: [INTERFACES] pgAdmin v6.4.2 Dave Page <dpage@vale-housing.co.uk>
@ 1999-02-12 15:12 ` David Hartwig <daveh@insightdist.com>
0 siblings, 0 replies; 6+ messages in thread
From: David Hartwig @ 1999-02-12 15:12 UTC (permalink / raw)
To: dpage@vale-housing.co.uk; +Cc: pgsql-interfaces
Dave Page wrote:
>
> > However, there is one item that you may want to address.
> > While browsing
> > through the Schema Tables, if I click on a column name I
> > often get an error.
> > "Error 3021, No current record." Perhaps I am doing
> > something incorrect.
> > The message only occurs when there in NO default value for
> > the column. I
> > inspected the ODBC driver CommLog and observed that, in
> > fact, pgadmin was
> > querying for these default values and was returning an empty
> > record sets.
> > This does not seem as if it should be considered an error condition.
>
> I'll look into this. I can't seem to reproduce it though, so if you could
> send me your CommLog and the c:\pgerr.log file it would be a help.
>
I have attached them both. Notice in the CommLog, the last query. I have
verified that no row meets the specified criteria. Only columns with DEFAULT
values seem to have entries in pg_attrdef.
>
> > If you ever get bored and are looking for something to do,
> > here are some ideas.
>
> I always looking to improve pgAdmin. The main constraint seems to be all
> this other work my employee seems to (somewhat unreasonably I think!) want
> finished.
>
> > 1. Implement a function and trigger management tool.
> > (I've been really
> > getting into this stuff lately.)
> > o Display all the triggers under each table and
> > which events they
> > respond to.
> > o Allow create/drop of triggers.
> > o Allow create/drop/edit of function - provide
> > simple editor
> > modify the text of plpgsql code.
>
> This and other things are on the ToDo list at the moment. The problem is
> that having never used triggers or functions etc. on any dbms at all, there
> is a bit of a learning curve - both in figuring out how the work, and then
> in getting the infomation on them from the relevant system tables.
>
> I'll get there eventually...
>
I saw your ToDo after I hit the send button.
I strongly recommend that you give triggers, and their required functions a
try. They are excellent as a mechanism for controlling the integrity of your
(anyone's) database. Once you try them (and the light goes on), you'll never
go back to letting applications dictate the rules (business rules) of your
data. A tool like the one your developing can only further my conviction.
Attachments:
psqlodbc_4294461495.log (application/x-unknown-content-type-log_auto_file, 9.8K) download
pgErr.log (application/x-unknown-content-type-log_auto_file, 1.1K) download
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] pgAdmin v6.4.2
@ 1999-02-17 10:40 Dave Page <dpage@vale-housing.co.uk>
1999-02-17 13:04 ` Re: [INTERFACES] pgAdmin v6.4.2 David Hartwig <daveh@insightdist.com>
0 siblings, 1 reply; 6+ messages in thread
From: Dave Page @ 1999-02-17 10:40 UTC (permalink / raw)
To: 'David Hartwig' <daveh@insightdist.com>; +Cc: pgsql-interfaces
Hi David,
I'm having real trouble figuring this one out. I've tried it on 95 & 98 and
on PostgreSQL 6.4 & 6.4.2 and cannot reproduce this error at all. I have
added code to handle if no default value can be found, but this should never
happen because the existing code will only try to get the default value if
the attribute record (pg_attribute.atthasdef) is true.
I'm not sure if this is because I've misunderstood the way PostgreSQL works
or there's some corruption in your system.
Any suggestions gratefully received :-)
Dave.
--
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!
> -----Original Message-----
> From: David Hartwig [mailto:daveh@insightdist.com]
> Sent: 12 February 1999 15:13
> To: Dave Page
> Cc: pgsql-interfaces@postgreSQL.org
> Subject: Re: [INTERFACES] pgAdmin v6.4.2
>
>
>
>
> Dave Page wrote:
>
> >
> > > However, there is one item that you may want to address.
> > > While browsing
> > > through the Schema Tables, if I click on a column name I
> > > often get an error.
> > > "Error 3021, No current record." Perhaps I am doing
> > > something incorrect.
> > > The message only occurs when there in NO default value for
> > > the column. I
> > > inspected the ODBC driver CommLog and observed that, in
> > > fact, pgadmin was
> > > querying for these default values and was returning an empty
> > > record sets.
> > > This does not seem as if it should be considered an error
> condition.
> >
> > I'll look into this. I can't seem to reproduce it though,
> so if you could
> > send me your CommLog and the c:\pgerr.log file it would be a help.
> >
>
> I have attached them both. Notice in the CommLog, the last
> query. I have
> verified that no row meets the specified criteria. Only
> columns with DEFAULT
> values seem to have entries in pg_attrdef.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [INTERFACES] pgAdmin v6.4.2
1999-02-17 10:40 RE: [INTERFACES] pgAdmin v6.4.2 Dave Page <dpage@vale-housing.co.uk>
@ 1999-02-17 13:04 ` David Hartwig <daveh@insightdist.com>
0 siblings, 0 replies; 6+ messages in thread
From: David Hartwig @ 1999-02-17 13:04 UTC (permalink / raw)
To: dpage@vale-housing.co.uk; +Cc: pgsql-interfaces
Bingo! Unset the "bool as char" in the Data Type Options of the Driver
Advanced Options and you should get the same error I am experiencing. In my
case, I simply set the option and it works great.
Dave Page wrote:
> Hi David,
>
> I'm having real trouble figuring this one out. I've tried it on 95 & 98 and
> on PostgreSQL 6.4 & 6.4.2 and cannot reproduce this error at all. I have
> added code to handle if no default value can be found, but this should never
> happen because the existing code will only try to get the default value if
> the attribute record (pg_attribute.atthasdef) is true.
>
> I'm not sure if this is because I've misunderstood the way PostgreSQL works
> or there's some corruption in your system.
>
> Any suggestions gratefully received :-)
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] pgAdmin v6.4.2
@ 1999-02-17 14:12 Dave Page <dpage@vale-housing.co.uk>
0 siblings, 0 replies; 6+ messages in thread
From: Dave Page @ 1999-02-17 14:12 UTC (permalink / raw)
To: 'David Hartwig' <daveh@insightdist.com>; +Cc: pgsql-interfaces
Of course - suddenly it all becomes crystal clear!
I've fixed this for the next release (which is coming very soon...). Please
let me know if you find anywhere else where this causes a problem.
Thanks,
Dave.
> -----Original Message-----
> From: David Hartwig [mailto:daveh@insightdist.com]
> Sent: 17 February 1999 13:05
> To: Dave Page
> Cc: pgsql-interfaces@postgreSQL.org
> Subject: Re: [INTERFACES] pgAdmin v6.4.2
>
>
> Bingo! Unset the "bool as char" in the Data Type Options of
> the Driver
> Advanced Options and you should get the same error I am
> experiencing. In my
> case, I simply set the option and it works great.
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~1999-02-17 14:12 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-02-11 16:06 pgAdmin v6.4.2 Dave Page <dpage@vale-housing.co.uk>
1999-02-12 08:32 RE: [INTERFACES] pgAdmin v6.4.2 Dave Page <dpage@vale-housing.co.uk>
1999-02-12 15:12 ` David Hartwig <daveh@insightdist.com>
1999-02-17 10:40 RE: [INTERFACES] pgAdmin v6.4.2 Dave Page <dpage@vale-housing.co.uk>
1999-02-17 13:04 ` David Hartwig <daveh@insightdist.com>
1999-02-17 14:12 RE: [INTERFACES] pgAdmin v6.4.2 Dave Page <dpage@vale-housing.co.uk>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox