Search Postgresql Archives

Re: Executing a Function with an INSERT INTO command fails

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 29, 2018 at 9:47 AM, TalGloz <glozmantal@xxxxxxxxx> wrote:

> Add "RAISE ERROR" to the top function's BEGIN block and verify that the
> next time you run your calling query it indeed fails.  I'm suspecting that
> the code you are iterating over is not the same code that is being
> executed
> (search_path dynamics probably).

Do you mean like this
BEGIN
RAISE NOTICE
.
.
INSERT INTO public.runtime_benchmark (test_number, column_names,
execution_time, operation_type, seal_or_sql) VALUES (1, 'Pickup_longitude,
Dropoff_longitude', '1', 'sub', 'seal');
.
.
END;

If I use RAISE ERROR i get ERROR:  unrecognized exception condition "error"


I was referring specifically to:


I was going for a conceptual communication, not syntax.

Though if you indeed get a syntax error then that precludes the "wrong object" theory.

David J.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux