anged
something. Still no schema showing for pgagent. Not sure anyone needs to
comment on this, but while issue seems to be solved, would like to know, is
the schema supposed to be somewhere?
novnov wrote:
>
> I have installed pgagent, apparently, but can't find it anywhere. I
> follow
I have installed pgagent, apparently, but can't find it anywhere. I followed
the instructions...from the postgres database, opened the query window,
installed plpgsql (installed as expected), ran the pgagent script. Success
reported. If I try to run the same script, I'm notified that it's already
novnov wrote:
> When 1.6 seems to have dropped varchar in favor of character varying.
> Shouldn't this be an option as opposed to an enforced behavior? I've read
> a
> little on the list about the change, but the problem is some packages I'm
> working with don
When 1.6 seems to have dropped varchar in favor of character varying.
Shouldn't this be an option as opposed to an enforced behavior? I've read a
little on the list about the change, but the problem is some packages I'm
working with don't recognize character varying. Maybe that will change over
ti
rom: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED] On Behalf Of novnov
>>Sent: donderdag 30 november 2006 3:59
>>To: pgadmin-support@postgresql.org
>>Subject: Re: [pgadmin-support] Can tables have calculated columns?
>>
>>Does no one know the answer to th
Does no one know the answer to this?
novnov wrote:
>
> I was under the impression that pgsql supported calculated columns in
> tables, but don't see a way to implement via pgAdmin and can't find
> anything on the subject in the pgsql docs. Are calculated columns
> sup
I just found out the same thing, running a test install on another pc. I must
have skipped that step with my screenshots.
Sorry for taking up so much bandwidth on this.
Raymond O wrote:
>
> On 28 Nov 2006 at 10:29, novnov wrote:
>
>> I've not actually reinstalled pgsql
nothing to adjust. I hesitated to remove and then
reinstall pgsql because I thought it might intro some other odd variable
into my pgsql issues...but I will if somehow that does allow access to the
contrib modules that are loaded. I'll test on another pc.
Raymond O wrote:
>
> On 28
and g_cube modules are included by default and ending with the
difficulty of manipulating template1...it could be easier for newbies.
Would it be possible in a future release of pgAdmin that access to these
settings can be adjusted?
Raymond O wrote:
>
> On 22 Nov 2006 at 17:21, novnov wrote
My 1.4.2 pgAdmin was installed with the windows version of postgres 8.1. I
pointed the 1.6.0 installer at the location that 1.4.2 was installed but
somehow both versions are still alive. I don't see a way to specifically
undo the 1.4.2 installation that came with pgsql. I don't see a need to have
I was under the impression that pgsql supported calculated columns in tables,
but don't see a way to implement via pgAdmin and can't find anything on the
subject in the pgsql docs. Are calculated columns supported?
--
View this message in context:
http://www.nabble.com/Can-tables-have-calculated
fusing to a newbie.
Thanks
Thomas Pundt wrote:
>
> Hi,
>
> On Thursday 23 November 2006 02:21, novnov wrote:
> | pgAdmin III is quite a nice tool but one thing I can't figure out is
> what
> | the difference is between what pgAdmin calls a function and what it
>
OK, thanks...and I take it that there is nothing about the cube functions
that are inherently needed? I've never touched template1, this is an out of
the box postgres 8.1 windows install.
Raymond O wrote:
>
> On 22 Nov 2006 at 17:21, novnov wrote:
>
>> Not sure this i
pgAdmin III is quite a nice tool but one thing I can't figure out is what the
difference is between what pgAdmin calls a function and what it calls a
procedure. They have almost the same properties in the edit dialog (but not
quite). I've looked in the postgres and pgAdmin help docs and there seem
mixed case naming, I could use
emp_fname, emp_lname, emp_org_id, but I'm not sure if that's best.
I am very curious to hear the various conventions folks here have arrived
at. I don't expect there to be consensus, but the various rationales might
help me arrive at an approach that work
if you or other have any
impressions re common practice. I'd guess most decide to use the "ItemName"
style, since double quoting would only be an issue under some circumstances
(like writing sprocs), and double quotes aren't a heavy burden anyways.
Dave Page-3 wrote:
>
>
ing list I seem to have been told
simply that the issue I ran into was due to a habit of pgAdmin. In a way you
confirm, but clarify that pdAdmin is doing it for 'my own good'?
Dave Page-3 wrote:
>
> novnov wrote:
>> I am having a discussion re pgsql double quoting or not in
s effectively preventing it? I like pgAdmin otherwise so I'd
prefer not to have to hunt down a different editor.
Dave Page-3 wrote:
>
> novnov wrote:
>> As far as I can tell pgsql itself does not require table and field names
>> to
>> be wrapped in double quotes,
I see, so to make it explicit, if I'd named my table item not Item, and the
column itemname not ItemName, pgAdmin (and pgsql) wouldn't need to double
quote. Not my preference but I'll live.
Thanks
Dave Page-3 wrote:
>
> novnov wrote:
>> As far as I can tell pgsql it
As far as I can tell pgsql itself does not require table and field names to
be wrapped in double quotes, but pgAdmin does that by default (at least on
windows). What's the rationale? I've not found a way to turn this off in
pgAdmin, is there a way, is it safe to do this?
It's a very nice package,
20 matches
Mail list logo
