I have wriiten following simple function in postgresql
CREATE OR REPLACE FUNCTION "MySchema".add_user(p_name character varying,
p_email1 character varying, p_email2 character varying)
RETURNS bigint AS
$BODY$
DECLARE
userId bigint;
BEGIN
INSERT INTO "MySchema"."
On 03.11.2011 13:32, Archana Sachin Ghag wrote:
I have wriiten following simple function in postgresql
CREATE OR REPLACE FUNCTION "MySchema".add_user(p_name character varying,
p_email1 character varying, p_email2 character varying)
RETURNS bigint AS
$BODY$
DECLARE
userId big
The following bug has been logged online:
Bug reference: 6285
Logged by: Gary Kenney
Email address: gary.ken...@xerox.com
PostgreSQL version: 9.1.1
Operating system: Windows 7
Description:PreparedStatement#executeUpdate gets syntax error on
apostrophe
Details:
The v
"Gary Kenney" writes:
> Description:PreparedStatement#executeUpdate gets syntax error on
> apostrophe
> The value that was assigned via PreparedStatement.setString, was "Gary's
> Document". Note the apostrophe. Without the apostrophe, there is no error.
Right offhand I would guess that
The following bug has been logged online:
Bug reference: 6286
Logged by: Greg Fausak
Email address: g...@named.com
PostgreSQL version: 9.1.1
Operating system: Linux
Description:Table Partitioning - SQL/MED - interaction broken
Details:
I create a table partition:
t
"Greg Fausak" writes:
> Here is the bug when trying to use the two together with a rule to bind
> them:
> create rule "_RETURN" as on select to X do instead select * from Y;
Creating rules on inheritance children isn't supported, and you should
not hold your breath waiting for it to be.
We prob
On Thu, Nov 3, 2011 at 10:57 AM, Greg Fausak wrote:
>
> I create a table partition:
>
> table M
>
> table A (check range) inherits M
> table B (check range) inherits M
> ...
> table X (check range) inherits M
>
> ASSERT: a query with constraint exclusions=on, performed on M will select
> the corre
