[HACKERS] Extended security/restriction to any role with login access

2008-06-25 Thread Domingo Alvarez Duarte
Hello ! I'm trying to use postgresql in an application that by design will give access to users to a subset of the database. For example for customers access to products_view (wich will only show public offers), orders (only their own orders). I'll provide an application as user interface for th

[HACKERS] Extended security/restriction to any role with login access

2008-06-25 Thread Domingo Alvarez Duarte
Hello ! I'm trying to use postgresql in an application that by design will give access to users to a subset of the database. For example for customers access to products_view (wich will only show public offers), orders (only their own orders). I'll provide an application as user interface for th

[HACKERS] bug in "create unique index"

2001-05-12 Thread Domingo Alvarez Duarte
when creating a index unique in a table that accept nulls the unique constraint doesn't work. Example: --- create table test_unique(i1 integer, i2 integer, unique(i1,i2); insert into test_unique(1,null); insert into test_unique(1,null); insert into test_unique(1,null); --- all "inserts" above in

[HACKERS] maybe a bug in plpgsql, nulls and empty strings are not the same

2001-05-28 Thread Domingo Alvarez Duarte
When trying write a function in plpgsql I'm getting behavior that probably isn't the corect one. in the function bellow: - -- split the given key create function dad_char_key_split( varchar,-- char_key integer,-- subkey_len char-- separator

[HACKERS] unique index doesn't accept functions on fields

2001-07-23 Thread Domingo Alvarez Duarte
I'm trying create a unique index using more than one field and applying a function in one field to achieve case insensitive uniqueness but postgresql doesn't accept. create table a( id int primary key, id2 int not null, name varchar(50), unique(id2, lower(name)) ); Anyone have an