hi,
When using row."open" and row."close" the function was working fine.
Many thanks for replying and help.
Mark
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Plpgsql-9-1-3-not-accepting-open-close-as-column-names-tp5657223p5657967.html
Sent from the PostgreSQL -
Hi,
On Sat, 2012-04-21 at 01:29 -0700, John R Pierce wrote:
> I tried installing 9.1 from the yum repo on a brand new minimal CentOS
> 6.1 x86_64 install and got an error.
>
> http://pgsql.privatepaste.com/04289a269b
> Resolution Error: Package: postgresql91-python-4.0-2PGDG.rhel6.x86_64
>
Hello,
you need to use quotes because open and close are sql key words
http://www.postgresql.org/docs/9.1/static/sql-keywords-appendix.html
row."open"
row."close"
Regards
From: fv967
To: pgsql-general@postgresql.org
Sent: Sunday, April 22, 2012 11:34
On 04/22/2012 02:34 AM, fv967 wrote:
Hi ,
I have the following function which was working fine in Postgresql 8.4.7
CREATE OR REPLACE FUNCTION insert_stockpricemerge1(startdate character
varying, enddate character varying)
RETURNS void AS
$BODY$
DECLARE
row RECORD;
BEGIN
FOR row
Hi ,
I have the following function which was working fine in Postgresql 8.4.7
CREATE OR REPLACE FUNCTION insert_stockpricemerge1(startdate character
varying, enddate character varying)
RETURNS void AS
$BODY$
DECLARE
row RECORD;
BEGIN
FOR row IN SELECT stockid, date, open, high, low
>
> If I understand it correct you need a statement playback solution.
> Here is some info about it
> http://wiki.postgresql.org/wiki/Statement_Playback.
>
Thanks Sergey,
I was reading and a I realized that maybe this can be useful.
--
Saludos,
Roberto De Oliveira
--
Sent via pgsql-general ma
