Ok, that works.
Another thing that was strange is that when I changed
declare _t1 s; to declare _t1 s[];
parsing passed, but of course it blew up at runtime.
Anyway, thanx for the workaround.
I'll see if it's faster comparing fields using record or as I do it currently.
Regards,
Rikard
The following bug has been logged on the website:
Bug reference: 7943
Logged by: Rikard Pavelic
Email address: rik...@ngs.hr
PostgreSQL version: 9.2.1
Operating system: Windows 7
Description:
ERROR: "_t1" is not a scalar variable
LINE 12: for _i1, _i2, _t1
The following bug has been logged on the website:
Bug reference: 7525
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1.2
Operating system: Windows 7
Description:
Is there a way in Postgres to create a unique constraint with
country *country; //this will create surrogate country_code field in address,
//function country(address) which returns
country
//and it would be great if it could
maintain relationship with country
}
Currently Postgres can't declare NOT NULL for town and reference from address
to country.
I would be happy if direction Postgres takes would allow design like this to be
enforced by database.
Regards,
Rikard
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 15.8.2012. 3:54, Craig Ringer wrote:
> On 08/14/2012 11:42 PM, Rikard Pavelic wrote:
>> On 8.8.2012. 13:30, Craig Ringer wrote:
>>> On 08/08/2012 06:24 PM, rikard.pave...@zg.htnet.hr wrote:
>>>> The following bug has been logged on the website:
>>>>
&g
On 8.8.2012. 13:30, Craig Ringer wrote:
> On 08/08/2012 06:24 PM, rikard.pave...@zg.htnet.hr wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 7485
>> Logged by: Rikard Pavelic
>> Email address: rikard.pave...@
The following bug has been logged on the website:
Bug reference: 7485
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: Unsupported/Unknown
Operating system: Windows
Description:
This is still an issue as reported in
http
On 21.6.2012. 6:03, Pavel Stehule wrote:
> 2012/6/21 Rikard Pavelic :
>> On 20.6.2012. 21:10, Tom Lane wrote:
>>> rikard.pave...@zg.htnet.hr writes:
>>>> create type t AS (i int); create type complex as (t t, i int); create
>>>> table bad(i int, c comple
x values(1,null);
insert into x values(2,(1,null));
insert into x values(3,(1,2));
--first row - ok
select * from x where c is null;
--last row - ok
select * from x where c is not null;
--unexpected result again
select c is null from x;
I must admit I was expecting
true
null
false
Regards,
R
On 20.6.2012. 20:55, Pavel Stehule wrote:
> Hello
>
> it is not a bug - see
> http://archives.postgresql.org/pgsql-hackers/2009-07/msg01525.php
>
> Regards
>
> Pavel Stehule
>
I found that in documentation after reporting bug.
I'm sorry for not searching some more, but didn't know where to look ex
The following bug has been logged on the website:
Bug reference: 6701
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1.3
Operating system: Windows 7
Description:
create type t AS (i int);
create type complex as (t t, i int
clone the database, I let our tool build it.
It built types with different order because our schema changed in the meantime.
Regards,
Rikard
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged on the website:
Bug reference: 6618
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1.3
Operating system: Windows 7
Description:
We've run into another issue with composite types.
I'
While I'm making up TODO's, my favorite one: support recursive types.
Regards,
Rikard
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
. If you
> want to store composite types in tables, I think you're better off
> using CREATE TYPE/ALTER TYPE.
I guess this falls under advanced type usage
(like recursive types - which can be used for lists)
which are not even recognized as important ;(
Regards,
Rikard
--
Sent via pgsql
The following bug has been logged on the website:
Bug reference: 6489
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1.2
Operating system: Windows 7
Description:
I'm trying to push types in Postgres and have run into
The following bug has been logged online:
Bug reference: 6058
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1 beta2
Operating system: Windows 7 64
Description:psql password prompt
Details:
psql doesn't hide passwo
The following bug has been logged online:
Bug reference: 6046
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1 beta 1
Operating system: Windows 7 64bit
Description:select current_date crashes postgres
Details:
select
On 15.4.2011 22:49, Kevin Grittner wrote:
> Rikard Pavelic wrote:
>> On 15.4.2011 21:06, Tom Lane wrote:
>>> The former.
>>>
>>> regression=# CREATE TYPE turtle AS
>>> (
>>> name varchar
>>> );
>>> CREATE TYPE
>
On 15.4.2011 21:06, Tom Lane wrote:
> The former.
>
> regression=# CREATE TYPE turtle AS
> (
> name varchar
> );
> CREATE TYPE
> regression=# ALTER TYPE turtle ADD ATTRIBUTE offspring turtle;
> ERROR: composite type turtle cannot be made a member of itself
> regression=#
>
>
The following bug has been logged online:
Bug reference: 5982
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1.alpha5
Operating system: Windows XP SP3
Description:recursive type crashes postgres
Details:
CREATE TYPE turtle
The following bug has been logged online:
Bug reference: 5970
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 9.1.alpha5
Operating system: Windows XP SP3
Description:intersect and collation on types
Details:
create table
The following bug has been logged online:
Bug reference: 4892
Logged by: Rikard Pavelic
Email address: rikard.pave...@zg.htnet.hr
PostgreSQL version: 8.4 beta2
Operating system: Windows XP SP3
Description:postmaster died and didn't restart
Details:
log of dea
23 matches
Mail list logo
