I'm getting these errors when importing dumps:
ERROR: relation "table1_id_seq" does not exist
ERROR: relation "table2_id_seq" does not exist
I renamed a couple tables, and the names of their
corresponding sequences remained the same. This causes
a problem because when importing - the create tab
On Thu, 2003-12-11 at 04:39, Keith C. Perry wrote:
> I think what the real religious argument here is that many, many people feel
> "skills assessment" should NOT be linked to a product. It should in fact be
> linked to the underlying material a product is designed to manipulate.
>
> If someone
I think though that there is an opportunity, though, for us to perhaps
work together in developing a Postgresql training base curriculum. We
can pool some resources and perhaps develop at least a list of the
things which ought to be covered. Perhaps this can lead to books on the
subject, etc. I a
Mike Nolan wrote:
I may need to move a web store to another hosting facility or rewrite it.
I'm currently exploring the Zelerate AllCommerce system
http://allcommerce.sourceforge.net
I haven't even reached the stage of installing it yet. It's designed to
run out-of-the-box on MySQL, so I'm a lit
I may need to move a web store to another hosting facility or rewrite it.
I will need to be able to tie it to the in-house order entry system
(which is/will be in Postgresql) for inventory status information.
Are there any commercial web store/shopping cart packages or host sites
that run under
Tom Lane said:
> Hm. By rights it *should* fail, since the ACL is clearly not granting
UPDATE permissions to anybody.
>
> The fact that it fails to fail seems to be because the rules on
> pg_settings rewrite the UPDATE into DO INSTEAD NOTHING (which does
nothing, in particular makes no permission
Quoting "Michael ." <[EMAIL PROTECTED]>:
> I am trying to move a postgresql database from one
> server to another. The original server is 7.1.3, and
> the new one is 7.3.4.
>
> I went on the old and used the command:
> pg_dumpall > dump
>
> On the new:
> psql -e < dump
>
> I get this for multi
I start PostgreSQL in the services utility under Redhat 9.0 with no issues.
PostgreSQL runs properly but as soon as I log out PostgreSQL shuts down. It
seems that I always need to be logged in for it to stay running.
I am running:
Redhat 9.0 Kernel 2.4.20-20.9
PostgreSQL 7.3.4-3.
[EMAIL PROTECTED] wrote:
Please, read this carefully: http://sql-info.de/mysql/
I can not believe it!
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
"Linux" training is not standardized by any measure either. Lots of
companies and "institutions" offer their own training courses. Some
of these grow to be fairly well recognized and are offered in similar
form repeatedly in different locations, but that is not
"standardized" in the sense y
"Linux" training is not standardized by any measure either. Lots of
companies and "institutions" offer their own training courses. Some of
these grow to be fairly well recognized and are offered in similar form
repeatedly in different locations, but that is not "standardized" in
the sense yo
Bret Busby wrote:
> Regarding the PostgreSQL training that is provided by companies, a
> problem with that, as it exists, is that, insofar as I am aware, that
> training is not standardised,
"Linux" training is not standardized by any measure either. Lots of
companies and "institutions" offer th
Tom Lane wrote:
Jean-Max Reymond <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
I think you need single quotes in that file. Try
datestyle='Postgres, European'
sorry, but it does not work with simple or double quotes :-(
Works for me (with single quotes). Did you remember to SIG
I am trying to move a postgresql database from one
server to another. The original server is 7.1.3, and
the new one is 7.3.4.
I went on the old and used the command:
pg_dumpall > dump
On the new:
psql -e < dump
I get this for multiple functions. (Error follows
surrounded by *'s)
CREATE FUN
Jean-Max Reymond <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I think you need single quotes in that file. Try
>> datestyle='Postgres, European'
>>
> sorry, but it does not work with simple or double quotes :-(
Works for me (with single quotes). Did you remember to SIGHUP the
postmaster (eg
Tom Lane wrote:
Jean-Max Reymond <[EMAIL PROTECTED]> writes:
3. datestyle="Postgres, European" in the postgresql.conf file, but
unfortunately it does nor work
I think you need single quotes in that file. Try
datestyle='Postgres, European'
sorry, but it does not work with simple or d
Jean-Max Reymond <[EMAIL PROTECTED]> writes:
> 3. datestyle="Postgres, European" in the postgresql.conf file, but
> unfortunately it does nor work
I think you need single quotes in that file. Try
datestyle='Postgres, European'
regards, tom lane
Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This fix may need to be rethought. I'm not sure though where is a clean
>> place to plug in the UPDATE permissions check given that the rules for
>> this case do not generate any UPDATE query.
> Do you want me to take a look at this, or
Tom Lane wrote:
Now, why does Florian see a permissions failure (which is really the
*right* behavior) when we don't? He didn't say exactly which PG version
he was running, but I see a likely-related bug fix between 7.3.2 and
7.3.3:
That seems to be it:
# psql regression
Welcome to psql 7.3.2, th
> That may be because there is no guarantee of the ordering of your returned
> records.
That makes sense - I just didn't think of it. Doh!
> Maybe you need to re-initialise your variables before executing the
> select?
I'm not sure what variables I could re-initialise here as the select
statemen
On 10/12/2003 09:10 John Sidney-Woollett wrote:
[snip]
Actually from my tests, the simple code below *sometimes* blocks on the
locked row, and sometimes skips the locked row, and returns the next
unlocked row.
That may be because there is no guarantee of the ordering of your returned
records.
[s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You've got to have some kind of "middleware". Apache, custom, whatever.
Basically this piece of middleware gets the session key.
Have the middleware (using a common login) retrieve the ser (and password)
drom the database table and authenticate the u
Dear All,
I wonder if anyone can advise me with this problem.
1. A user logs into the database (through web, webservice, some other piece
of software) - connect(user="joe",passwd="blogs")
2. We generate a random session key which will expire in 1 hour. Put this in
table (user, SessKey, time).
3
Thanks Oleg, I'll take a look at it. Too bad there is no documentation.
Also, there's something wrong with 'trgm.tgz'. This is what happens if I
try to extract it's contents :
gzip: stdin is encrypted -- get newer version of gzip
tar: End of archive volume 1 reached
tar: Sorry, unable to determi
Thanks Oleg, I'll take a look at it. Too bad there is no documentation.
Also, there's something wrong with 'trgm.tgz'. This is what happens if I
try to extract it's contents :
gzip: stdin is encrypted -- get newer version of gzip
tar: End of archive volume 1 reached
tar: Sorry, unable to determi
On Tuesday 09 December 2003 14:56, Tom Lane wrote:
> plpgsql is effectively doing
>
> regression=# select textin(point_out('(1,2)'::point));
> textin
>
> (1,2)
> (1 row)
>
> There is not a one-step cast function for this. (Not for any
> fundamental reason, just a lack of round tuits.)
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Although you certainly have a point that a lot of companies rely on
"certification" in the one or other way, you'd have to admit that probably
80% of "certified" people have no clue what they are talking about.
I met so many certified people where y
Well, maybe I forgot to mention that I'm not aware of any large objects
that had to be migrated. All data I put into the db was just VARCHARs,
INTEGERs and some SERIALs.
How can I find out more about the "missing" objects and where they are
queried?
Dirk Försterling wrote:
2003-11-29 15:19:54 [1359
Florian G. Pflug wrote:
I installed a postgres-application (which was developed on debian woody)
on red hat 9 today, using the postgres 7.3 rpms from redhad.
One of my the triggers uses the pg_settings table (more precisely, it
updates that table to change the search_path temporarily). With the
Martijn van Oosterhout wrote:
Thanks, I've never seen that page before. I guess it must be new.
There may be more elegant ways to do this, and I'm sure this is
incomplete/could be improved upon, but just for grins:
---
create type us
Dear Philippe Lang,
For e-mail from PgSQL function you need is
http://pgmail.sourceforge.net/
Tell me if it help's n one of my project its a great help
Regards,
V Kashyap
---(end of broadcast)---
TIP 8: explain analyze is your friend
Hi
I installed a postgres-application (which was developed on debian
woody) on red hat 9 today, using the postgres 7.3 rpms from redhad.
One of my the triggers uses the pg_settings table (more precisely, it
updates that table to change the search_path temporarily). With the
postgres 7.3 (and 7.
On Tue, 9 Dec 2003, Bryan Encina wrote:
> Date: Tue, 9 Dec 2003 15:06:05 -0800
> From: Bryan Encina <[EMAIL PROTECTED]>
> To: 'Bruce Momjian' <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: [NOVICE] PostgreSQL Training
>
> > I think that is about the author of the web site, and is
> >
33 matches
Mail list logo
