Re: [BUGS] BUG #2952: where is the user guide

2007-02-01 Thread Peter Eisentraut
Jessica wrote: > Description:where is the user guide That is a usage question, not a bug report. Perhaps you want to join the pgsql-novices list to learn about using PostgreSQL. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)-

Re: [BUGS] BUG #2953: index scan, feature request

2007-02-01 Thread Tom Lane
"michael" <[EMAIL PROTECTED]> writes: > can these be executed with index seek like what MS SQL does? > select * from account_category > where account_category_full_description <> 'MICHAEL' What for? A query like that is generally going to fetch the majority of the table, so an indexscan would be

[BUGS] BUG #2953: index scan, feature request

2007-02-01 Thread michael
The following bug has been logged online: Bug reference: 2953 Logged by: michael Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.0 Operating system: windows 2000 Description:index scan, feature request Details: hi postgresql team, can these be executed wit

[BUGS] BUG #2952: where is the user guide

2007-02-01 Thread Jessica
The following bug has been logged online: Bug reference: 2952 Logged by: Jessica Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2 Operating system: unix Description:where is the user guide Details: I installed it one month ago. 1. How can I log in and conne

Re: [BUGS] BUG #2948: default null values for not-null domains

2007-02-01 Thread Sergiy Vyshnevetskiy
On Thu, 1 Feb 2007, Tom Lane wrote: Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes: If input function IS strict then nulls are ALWAYS accepted. If input function IS NOT strict then nulls MIGHT be rejectted. And the patch is much more simple now (attached). Is that it? Almost right. exec_ass

Re: [BUGS] BUG #2954: null is not checked against domain constraints in return clause

2007-02-01 Thread Tom Lane
Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes: > I believe the bug to be here: >/* Normal case for scalar results */ >estate->retval = exec_eval_expr(estate, stmt->expr, >&(estate->retisnull), >&(estate->rettype)); > in exec_stmt_re

Re: [BUGS] BUG #2948: default null values for not-null domains

2007-02-01 Thread Tom Lane
Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes: > If input function IS strict then nulls are ALWAYS accepted. > If input function IS NOT strict then nulls MIGHT be rejectted. > And the patch is much more simple now (attached). > Is that it? Almost right. exec_assign_value() thinks its isNull arg

Re: [BUGS] BUG #2948: default null values for not-null domains

2007-02-01 Thread Sergiy Vyshnevetskiy
On Thu, 1 Feb 2007, Tom Lane wrote: Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes: Why not add PLPGSQL_TTYPE_DOMAIN and rename PLPGSQL_TTYPE_SCALAR to PLPGSQL_TTYPE_BASE? We only use PLPGSQL_TTYPE_SCALAR in _3_ places! That was my first thought too, but it's wrong. The right thing is to lo

Re: [BUGS] BUG #2948: default null values for not-null domains

2007-02-01 Thread Tom Lane
Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes: > Why not add PLPGSQL_TTYPE_DOMAIN and rename PLPGSQL_TTYPE_SCALAR to > PLPGSQL_TTYPE_BASE? We only use PLPGSQL_TTYPE_SCALAR in _3_ places! That was my first thought too, but it's wrong. The right thing is to look at the strictness of the input fu

Re: [BUGS] BUG #2954: null is not checked against domain constraints in return clause

2007-02-01 Thread Sergiy Vyshnevetskiy
I believe the bug to be here: /* Normal case for scalar results */ estate->retval = exec_eval_expr(estate, stmt->expr, &(estate->retisnull), &(estate->rettype)); in exec_stmt_return() in pl_exec.c. As I understand it, exec_eval_expr overwr

[BUGS] BUG #2954: null is not checked against domain constraints in return clause

2007-02-01 Thread Sergiy Vyshnevetskiy
The following bug has been logged online: Bug reference: 2954 Logged by: Sergiy Vyshnevetskiy Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.1 Operating system: FreeBSD-6 stable Description:null is not checked against domain constraints in return clause Deta

Re: [BUGS] BUG #2948: default null values for not-null domains

2007-02-01 Thread Sergiy Vyshnevetskiy
On Thu, 1 Feb 2007, Peter Eisentraut wrote: Tom Lane wrote: I'm starting to get the feeling that the entire idea of NOT NULL domains is broken :-( How is that so very different from having a default value of 5 with a domain that rejects 5? Because 5 will be rejected as a value for a variabl

Re: [BUGS] BUG #2948: default null values for not-null domains

2007-02-01 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> I'm starting to get the feeling that the entire idea of NOT NULL >> domains is broken :-( > How is that so very different from having a default value of 5 with a > domain that rejects 5? Two words for you: outer joins.

Re: [BUGS] BUG #2948: default null values for not-null domains

2007-02-01 Thread Sergiy Vyshnevetskiy
On Wed, 31 Jan 2007, Tom Lane wrote: Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes: Not at all. What's "broken" is the idea of variable as a simple piece of memory. It is correct for base types, but not for domains - they may have non-empty constructors (in C++ terminology). That may be, bu

Re: [BUGS] BUG #2948: default null values for not-null domains

2007-02-01 Thread Peter Eisentraut
Tom Lane wrote: > I'm starting to get the feeling that the entire idea of NOT NULL > domains is broken :-( How is that so very different from having a default value of 5 with a domain that rejects 5? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end o