Take a look at http://www.postgresql.org/docs/8.3/interactive/plpgsql-cursors.html
and you'll find answer you need.

--
Best regards, Yuri.

Nacef LABIDI gmail.com> schrieb:

Try 'select * from my_function();'

Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°

Hello

I have an XML file, which i must import into the database. I transform
this XML File with xslt to sql INSERTS.

But there is also the possibility, that one row is available. Means that
i need an UPDATE instead of the INSERT.

Is it in SQL possible to decide if there is an UPDATE or an INSERT or
must i program something with PHP for example?

Thanks
Andreas

Xavier Bermeo wrote:

Assuming you're using ECPG, there are a couple of examples in the
documentation, e.g.,

http://www.postgresql.org/docs/8.3/static/ecpg-commands.html
(see Select using cursors:

http://www.postgresql.org/docs/8.3/static/ecpg-variables.html#AEN33442

The essence is you DECLARE the cursor, OPEN it and then FETCH rows in
some kind of loop, and finish by CLOSE cursor. To exit the loop, you
can check sqlca.sqlcode for 100 (NOT FOUND) or a SQLSTATE of 02000.

At 12:20 PM 8/15/2008, pgsql-sql-owner@postgresql.org wrote:

Might have luck with applying some additional WHERE clause criteria to
your full outer join. So if you don't want certain types NULL's in
table b, restrict against that in WHERE clause? I could be
misunderstanding the whole thing though..

Steve

On Thu, Aug 07, 2008 at 10:55:17PM -0400, Joe wrote:

I gather that the general consensus is that Oracle and Postgresql are
different enough that I will have to figure them out independently. I
have found that Postgresql is more tolerant of operator ignorance, so
I had hoped that any Oracle solution would work elsewhere, but maybe
not.

Thanks for the helpful responses.

--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

felix@crowfix.com wrote:

I suggest you do not assume that Oracle implementation details apply to
Postgres, because they do not, most of the time. They certainly don't
in this case.

Jorge Medina wrote:

Out of interest - why 1000 connections?

Do you really expect to have 1000 jobs concurrently active and doing
work? If you don't, then you'll be wasting resources and slowing things
down for no reason. There is a connection overhead in PostgreSQL - IIRC
mostly related to database-wide locking and synchronization, but also
some memory for each backend - that means you probably shouldn't run
vastly more backends than you intend to have actively working.

If you described your problem, perhaps someone could give you a useful
answer. Your mention of pgpool suggests that you're probably using a web
app and running into connection count limits, but I shouldn't have to
guess that.

--
Craig Ringer

In the application that we are working on, all data searches must be case insensitive.

Select * from test where column1 = 'a' and Select * from test where column1 = 'A' should always be the same and use the index if column1 is indexed. In order to do this am I going to be required to use the lower() on all selects in order to make sure that they are case insensitive? In some db's if you use a lower() or upr() it will always do a table scan instead of using a index

Best Regards,

Michael Gould, Manager Information Technology
All Coast Intermodal Services, Inc.
First Coast Intermodal Services, Inc.
First Coast Logistical Services, LLC.
904-226-0978

BODY{font:10pt Tahoma, Verdana, sans-serif;}

In the application that we are working on, all data searches must be case insensitive. 
 
Select * from test where column1 = 'a' and Select * from test where column1 = 'A' should always be the same and use the index if column1 is indexed.  In order to do this am I going to be required to use the lower() on all selects in order to make sure that they are case insensitive?  In some db's if you use a lower() or upr() it will always do a table scan instead of using a indexBest Regards,Michael Gould, Manager Information TechnologyAll Coast Intermodal Services, Inc.First Coast Intermodal Services, Inc.First Coast Logistical Services, LLC.904-226-0978
 
 

There are no synonyms in Postgres (like in Oracle).
To implement what you want, you need to use views and rules.
From Postgres docs:
"Currently, views are read only: the system will not allow an insert,
update, or delete on a view. You can get the effect of an updatable view
by creating rules that rewrite inserts, etc. on the view into
appropriate actions on other tables."

Read docs on views and rules.

HTH,
Igor

-----Original Message-----
From: pgsql-sql-owner@postgresql.org
[mailto:pgsql-sql-owner@postgresql.org] On Behalf Of Tk421
Sent: Friday, July 25, 2008 8:13 AM
To: pgsql-sql@postgresql.org
Subject: [SQL] A table with two names or table alias

Can I create a table name alias?

What i want is to access the same table with two different names. An
example: