The other option would be to create temp table...
Execute dynamic sql to fil temp table
Copy from temp table - copy will return number of rowsx (not inside
execute...)
Drop temp
Kind regards,
Misa
On Wednesday, January 16, 2013, Misa Simic wrote:
> I meant the count from the same query as fo
I meant the count from the same query as for copy command what actually go
to file... Not count rows from table...
But i agree could be slow...
Cheers,
Misa
On Wednesday, January 16, 2013, James Sharrett wrote:
> The # rows in the table <> # rows in the file because the table is grouped
> an
On 01/16/2013 09:26 AM, James Sharrett wrote:
Integer
Well copy is returning a string, so try changing the type. You will have
to parse that string for the count.
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your
Integer
On 1/16/13 12:21 PM, "Adrian Klaver" wrote:
>On 01/16/2013 09:16 AM, James Sharrett wrote:
>> The problem I have is that I get nothing back when the COPY is run
>>inside
>> the function other than what I explicitly return from the function so I
>> don't have anything to parse. It's od
On 01/16/2013 09:16 AM, James Sharrett wrote:
The problem I have is that I get nothing back when the COPY is run inside
the function other than what I explicitly return from the function so I
don't have anything to parse. It's odd that the record count in the
function is treated differently than
2013/1/16 James Sharrett :
> I have a function that generates a table of records and then a SQL statement
> that does a COPY into a text file. I want to return the number of records
> output into the text file from my function. The number of rows in the table
> is not necessarily the number of ro
The problem I have is that I get nothing back when the COPY is run inside
the function other than what I explicitly return from the function so I
don't have anything to parse. It's odd that the record count in the
function is treated differently than from sql query in GET DIAGNOSTIC
since the form
The # rows in the table <> # rows in the file because the table is grouped
and aggregated so simple table row count wouldn't be accurate. The table
can run in the 75M - 100M range so I was trying to avoid running all the
aggregations once to output the file and then run the same code again just
to
Hi
Maybe:
1.
strSQL := 'copy (select MyColumns from MyExportTable) to MyFile.csv with
CSV HEADER;';
Execute strSQL
strSQL := 'Select count(*) from (select MyColumns from MyExportTable) t';
Execute strSQL into export_count;
Return export_count;
Kind Regards,
Misa
On Wednesday, January 16,
On 01/16/2013 08:30 AM, James Sharrett wrote:
I have a function that generates a table of records and then a SQL
statement that does a COPY into a text file. I want to return the
number of records output into the text file from my function. The
number of rows in the table is not necessarily the
On 01/16/2013 09:30 AM, James Sharrett wrote:
I have a function that generates a table of records and then a SQL
statement that does a COPY into a text file. I want to return the
number of records output into the text file from my function. The
number of rows in the table is not necessarily the
I have a function that generates a table of records and then a SQL statement
that does a COPY into a text file. I want to return the number of records
output into the text file from my function. The number of rows in the table
is not necessarily the number of rows in the file due to summarization
12 matches
Mail list logo
