Thread: The old pl/pgsql editor question back again

The old pl/pgsql editor question back again

From
"Garcia, Joshua"
Date:

Have better editors popped up for pl/pgsql since the last discussion about pl/pgsql editors in the mailing lists?  Or have the features for the most popular pl/pgsql editors improved since the last discussion?

 

Thanks in advance,

Josh

Re: The old pl/pgsql editor question back again

From
"Andrej Ricnik-Bay"
Date:
> Have better editors popped up for pl/pgsql since the last discussion about
> pl/pgsql editors in the mailing lists?  Or have the features for the most
> popular pl/pgsql editors improved since the last discussion?
Does this one come close to what you want?
http://www.emacswiki.org/cgi-bin/wiki/sql.el

And no, I didn't search the archive for the old thread.


> Thanks in advance,
>
> Josh
Cheers,
Andrej

Re: The old pl/pgsql editor question back again

From
"Nikolay Samokhvalov"
Date:
On 8/3/06, Garcia, Joshua <Joshua.Garcia@xerox.com> wrote:
> Have better editors popped up for pl/pgsql since the last discussion about
> pl/pgsql editors in the mailing lists?  Or have the features for the most
> popular pl/pgsql editors improved since the last discussion?
>

EMS SQL Manager seems to be the best for me. I don't know other tool
that allows to debug pl/pgsql functions. But it costs... But not so
much :-)

--
Best regards,
Nikolay

Re: The old pl/pgsql editor question back again

From
John DeSoi
Date:
On Aug 3, 2006, at 11:59 AM, Garcia, Joshua wrote:

> Have better editors popped up for pl/pgsql since the last
> discussion about pl/pgsql editors in the mailing lists?  Or have
> the features for the most popular pl/pgsql editors improved since
> the last discussion?


What features are you looking for that existing products don't have?


John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL


Re: The old pl/pgsql editor question back again

From
"Garcia, Joshua"
Date:
I just tried out your editor and it looks pretty good.  There are two
features I would deem absolutely necessary that no single editor I have
used seems to have.  These are:
- syntax highlighting that is smart enough to look akward when a syntax
error is made.  I think nedit does a pretty good job of this.  emacs
syntax highlighting I've tried is pretty weak, but I really like emacs
and use it a lot.
- smart indention like emacs has in its c-mode.  I've seen editors have
no automatic/smart indention or the indention just doesn't work properly
for pl/pgsql

Josh

-----Original Message-----
From: John DeSoi [mailto:desoi@pgedit.com]
Sent: Friday, August 04, 2006 4:30 AM
To: Garcia, Joshua
Cc: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] The old pl/pgsql editor question back again


On Aug 3, 2006, at 11:59 AM, Garcia, Joshua wrote:

> Have better editors popped up for pl/pgsql since the last
> discussion about pl/pgsql editors in the mailing lists?  Or have
> the features for the most popular pl/pgsql editors improved since
> the last discussion?


What features are you looking for that existing products don't have?


John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL


Re: The old pl/pgsql editor question back again

From
John DeSoi
Date:
On Aug 4, 2006, at 10:55 AM, Garcia, Joshua wrote:

> - syntax highlighting that is smart enough to look akward when a
> syntax
> error is made.  I think nedit does a pretty good job of this.  emacs
> syntax highlighting I've tried is pretty weak, but I really like emacs
> and use it a lot.

This is pretty hard without a full blown parser.

> - smart indention like emacs has in its c-mode.  I've seen editors
> have
> no automatic/smart indention or the indention just doesn't work
> properly
> for pl/pgsql

Do you mean it automatically indents things? That is, it changes the
indentation level for you? In a previous message you wrote:

> indent .sql files the way nedit indents
> them (which is indenting them at the same place of the line above
> while retaining sql syntax highlighting)?

If I understand correctly, pgEdit does this (keeps the indentation
level of the previous line). But it does not try to guess a different
indentation level of the next line based on the surrounding syntax.



John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL


Re: The old pl/pgsql editor question back again

From
"Garcia, Joshua"
Date:
On Aug 4, 2006, at 10:55 AM, Garcia, Joshua wrote:

>> - syntax highlighting that is smart enough to look akward when a
>> syntax
>> error is made.  I think nedit does a pretty good job of this.  emacs
>> syntax highlighting I've tried is pretty weak, but I really like
emacs
>> and use it a lot.

> This is pretty hard without a full blown parser.

Ya, I probably don't care about this one so much.  No editor for
pl/pgsql I've seen so far does this.  I've managed to go on pretty well
without it.  I can probably live without it, but I think it's a really
useful feature.

>> - smart indention like emacs has in its c-mode.  I've seen editors
>> have
>> no automatic/smart indention or the indention just doesn't work
>> properly
>> for pl/pgsql>

>Do you mean it automatically indents things? That is, it changes the
>indentation level for you? In a previous message you wrote:

>> indent .sql files the way nedit indents
>> them (which is indenting them at the same place of the line above
>> while retaining sql syntax highlighting)?

Hehe...you remembered that.  I wanted emacs to indent like how nedit and
pgedit do, but it looks like I'd have to edit sql-mode or
sql-interactive-mode.  I don't have time for that. :-(

> If I understand correctly, pgEdit does this (keeps the indentation
> Level of the previous line). But it does not try to guess a different

> indentation level of the next line based on the surrounding syntax.

Ya, exactly.  pgEdit and nedit, unlike emacs, automatically keeps the
indentation of the previous line for .sql files.  But having the
indentation work based on surrounding syntax I find to be really useful
because slight changes in code require irritating amounts of indentation
changes.  Like I find I have to change conditional statements, now I
have to reformat a bunch of if statements or switch statements.

There are probably better uses of a developer's time than implementing
such features.  But for me personally, just those two features save me
tons of time and effort.  I think I just find readability of code to be
very valuable.

Josh