Re: [BUGS] BUG #2649: wish: provide multi-row INSERT with VALUES

2006-09-25 Thread Harald Armin Massa
Maciej,this feature is scheduled for PostgreSQL 8.2 and allready in the release notes of that release, coming most likely eoty.HaraldOn 9/24/06, 
Maciej Pilichowski <[EMAIL PROTECTED]> wrote:
The following bug has been logged online:Bug reference:  2649Logged by:  Maciej PilichowskiEmail address:  [EMAIL PROTECTED]PostgreSQL version: 
8.0.3Operating system:   opensuse 10.0Description:wish: provide multi-row INSERT with VALUESDetails:There is:INSERT ...VALUES (...);however it would be a nice extension to have:
INSERT ...VALUES(...), -- the first row with values(...), -- the 2nd(...); -- the 3rd, etc.---(end of broadcast)---TIP 5: don't forget to increase your free space map settings
-- GHUM Harald Massapersuadere et programmareHarald Armin MassaReinsburgstraße 202b70197 Stuttgart0173/9409607-Python: the only language with more web frameworks than keywords.
 -- Harald A. Massa, December 2005 http://groups.google.de/group/comp.lang.python/browse_thread/thread/285b9adeec188fb2



Re: [BUGS] BUG #2648: I can not create table name with capital and small characters

2006-09-25 Thread Harald Armin Massa
Asaf,this is not a bug. To use identifier names (identfiers = column-names, table-names, view-names...) with capital and small characters, you need to doublequote those names.So you can do select "Asaf" from "Avraham"
but not select Asaf from Avraham. This behaviour is documented and intended.Best wishes,HaraldOn 9/24/06, Asaf Avraham
 <[EMAIL PROTECTED]> wrote:
The following bug has been logged online:Bug reference:  2648Logged by:  Asaf AvrahamEmail address:  [EMAIL PROTECTED]PostgreSQL version: 
8.1.4.2Operating system:   winDescription:I can not create table name with capital and smallcharactersDetails:I have table that contain name with capital and small characters (ex.
tblEmp). In the columns is the same (ex. EmpID).In Creating table postgres add inverted commas on the nameWhen I'm running any query on this table i get:1. select * from tblEmp   Get: ERROR:  relation "tblemp" does not exist
2. select * from "tblEmp"   Get: ResultedThanks---(end of broadcast)---TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not   match-- GHUM Harald Massapersuadere et programmareHarald Armin MassaReinsburgstraße 202b
70197 Stuttgart0173/9409607-Python: the only language with more web frameworks than keywords. -- Harald A. Massa, December 2005 
http://groups.google.de/group/comp.lang.python/browse_thread/thread/285b9adeec188fb2


Re: [BUGS] BUG #2644: pgadmin III foreign key

2006-09-25 Thread Dave Page
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Massimiliano Citterio
> Sent: 22 September 2006 09:21
> To: pgsql-bugs@postgresql.org
> Subject: [BUGS] BUG #2644: pgadmin III foreign key
> 
> 
> The following bug has been logged online:
> 
> Bug reference:  2644
> Logged by:  Massimiliano Citterio
> Email address:  [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operating system:   Windows 2003
> Description:pgadmin III  foreign key
> Details: 
> 
> The referencing column dropdown listbox not filled with fields from
> referenced table.
> 
> The case appear after doing the following actions.
> 
> Create a schema named like $user (ex. "postgres").
> Delete Schema "Public".
> Refresh the Database View...
> Now the default Schema for the database is "postgres"
> 
> create tables, the try to create foreign keys using the GUI.
> There is no way.
> 
> If you create a new schema "public" it does not works.
> 
> If you create a new schema "public" and rename the "postgres" 
> schema to
> something else the it works.
> 
> If you drop schema "postgres" create schema "public" and then recreate
> schema postgres and his tables, then foreign key GUI works.
> 
> May be the GUI search for schema "public" but it must have an 
> OID lesser of
> all other schemas in the searchpath.
> 
> Infact the default search path is $user, public.
> 
> By the way it does not work if a schema named public does not exist.

I cannot reproduce this in the 1.6 development code - can you test beta
1 please?

Regards, Dave.

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [BUGS] BUG #2648: I can not create table name with capital and small characters

2006-09-25 Thread Harald Armin Massa
Asaf,SQL-92 states that identifiers [for dictionary
objects] are limited to 128 characters and are case-insensitive (unless delimited
by double quotes), because they are automatically translated into uppercase
by the system.Standards are SQL-92, SQL-99 and SQL-2003, done by ISO and other standardization commitees.It can be that JSP and ASP work different than standard SQL-92. I formyself prefer the easiest solution: just not use mixed case identifiers.
Best wishes,HaraldOn 9/25/06, Asaf Avraham <[EMAIL PROTECTED]> wrote:
Harald,
This is the point, i need to  use standard sql (from jsp, asp). and quote is not a standard 
Thanks
Asaf. 
On 9/25/06, Harald Armin Massa <[EMAIL PROTECTED]
> wrote:
Asaf,this is not a bug. To use identifier names (identfiers = column-names, table-names, view-names...) with capital and small characters, you need to doublequote those names.
So you can do select "Asaf" from "Avraham" but not select Asaf from Avraham. This behaviour is documented and intended.Best wishes,Harald

On 9/24/06, Asaf Avraham <[EMAIL PROTECTED]
> wrote: 
The following bug has been logged online:Bug reference:  2648Logged by:  Asaf Avraham
Email address:  [EMAIL PROTECTED]PostgreSQL version: 

8.1.4.2Operating system:   winDescription:I can not create table name with capital and smallcharactersDetails:I have table that contain name with capital and small characters (ex. 
tblEmp). In the columns is the same (ex. EmpID).
In Creating table postgres add inverted commas on the nameWhen I'm running any query on this table i get:1. select * from tblEmp   Get: ERROR:  relation "tblemp" does not exist 2. select * from "tblEmp"
   Get: ResultedThanks---(end of broadcast)---TIP 9: In versions below 8.0, the planner will ignore your desire to    choose an index scan if your joining column's datatypes do not
   match-- GHUM Harald Massapersuadere et programmareHarald Armin MassaReinsburgstraße 202b 70197 Stuttgart0173/9409607
-Python: the only language with more web frameworks than keywords.-- Harald A. Massa, December 2005 

http://groups.google.de/group/comp.lang.python/browse_thread/thread/285b9adeec188fb2 

-- GHUM Harald Massapersuadere et programmareHarald Armin MassaReinsburgstraße 202b70197 Stuttgart0173/9409607-Python: the only language with more web frameworks than keywords.
 -- Harald A. Massa, December 2005 http://groups.google.de/group/comp.lang.python/browse_thread/thread/285b9adeec188fb2



Re: [BUGS] Out of memory error during large hashagg

2006-09-25 Thread Casey Duncan


On Sep 24, 2006, at 8:59 AM, Tom Lane wrote:


Casey Duncan <[EMAIL PROTECTED]> writes:

seed  | st_id   | 164656



I ran analyze after this, but the results were roughly the same.


What's the statistics target set to, and did you try increasing it?
Can we see the rest of the pg_stats row for this column (I'm mainly
interested in the most-common-value frequencies)?


Here's the full pg_stats row:

 public | seed  | st_id | 0 | 8 | 138674  
|  
{42151109694333522,66226913946054313,108711403296197641,1351772151143018 
06,1130147629642373,1597650524892734,16434507676114329,17430059620571257 
,22269564345616346,28879557667799977} |  
{0.001,0.001,0.001,0.001,0.00067,0.00067,0.00067,0.00067 
,0.00067,0.00067} |  
{69337952030227,23194309459225658,44727149474281842,67399809385152536,93 
773403960447474,116874916355760832,138282618203581456,141866119873210938 
,145491433047267294,149167246450593786,152782384850071963} |0.829168


I haven't tried increasing the stats target. What would be a suitable  
value to try?


Thanks

-Casey


---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly


Re: [BUGS] Out of memory error during large hashagg

2006-09-25 Thread Tom Lane
Casey Duncan <[EMAIL PROTECTED]> writes:
> I haven't tried increasing the stats target. What would be a suitable  
> value to try?

Try 100 (instead of the default 10) ... you can go as high as 1000,
though hopefully that's overkill.

regards, tom lane

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org


[BUGS] BUG #2651: 8.2 - beta 1 does now compile with Sun Studio 11

2006-09-25 Thread Remy Beaumont

The following bug has been logged online:

Bug reference:  2651
Logged by:  Remy Beaumont
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.2 - beta 1
Operating system:   Solaris 10 on T2000
Description:8.2 - beta 1 does now compile with Sun Studio 11
Details: 

When we try to compile 8.2 - beta 1 on a T2000 wth Sun Studio 11, the build
fails at the following file: 

make[5]: Entering directory
`/usr/home/remy/postgresql-8.2beta1/src/backend/utils/adt'
/opt/SUNWspro/bin/cc -Xa -xtarget=ultraT1 -fast -I../../../../src/include  
-c -o float.o float.c
"float.c", line 112: identifier redeclared: cbrt
current : static function(double) returning double
previous: function(double) returning double :
"/usr/include/iso/math_c99.h", line 126
cc: acomp failed for float.c
make[5]: *** [float.o] Error 2


The flags used for compiling are:  CC=/opt/SUNWspro/bin/cc
'CFLAGS=-xtarget=ultraT1 -fast'

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


[BUGS] Alertbox: 6 Ways to Fix a Confused Information Architecture

2006-09-25 Thread Jakob Nielsen
Jakob Nielsen's Alertbox for September 25 is now online at:
  > http://www.useit.com/alertbox/ia.html

Summary:
When your website's users consistently go to the wrong sections, you have
many options for getting users back on track, from better labels to
clearer structure.



User Experience 2006 conference

  > Seattle, October 22-28 
  > London, November 5-11 

Full conference program, with list of 29 full-day tutorials:

  > http://www.nngroup.com/events

Your conference ticket includes access to all three keynote talks plus the
networking reception, no matter what days you are otherwise registered to
attend.

Deadline to save 10% on London registration: NEXT FRIDAY, Oct. 6



Response Time as Trade Barrier

One of the main reasons Baidu is winning search share in China over
Google, Yahoo, and MSN is that users complain that the foreign search
engines are too slow. Of course, it's well-known that download times is a
key factor in usability and that users prefer fast sites. What's less
well-known is that the reason for the slow performance of the GYM sites is
that the Chinese government has artificially reduced the speed of
accessing sites outside China.

China should be reported to the WTO for restraint of trade for delaying
foreign websites' download times.

I strongly doubt that the State Department has anybody at the policy level
who understands usability, so most likely nothing will happen. With the
growth of the digital economy, usability becomes an increasingly important
element in determining which products and services customers choose to
patronize. This again means that trade negotiators to understand ways in
which facilitate or undermine good user experience.



Visiting the Old Country:
Intranet seminar in Copenhagen, Denmark on Nov. 14

  > http://www.intrateam.dk/Seminarer/Intranet_Usability.aspx


---
Nielsen Norman Group, 48105 Warm Springs Blvd, Fremont, CA 94539 USA
To subscribe send blank email to [EMAIL PROTECTED] 
To unsubscribe send blank email to [EMAIL PROTECTED]
[You are currently subscribed as [EMAIL PROTECTED]

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [BUGS] BUG #2651: 8.2 - beta 1 does now compile with Sun Studio 11

2006-09-25 Thread Tom Lane
"Remy Beaumont" <[EMAIL PROTECTED]> writes:
> When we try to compile 8.2 - beta 1 on a T2000 wth Sun Studio 11, the build
> fails at the following file: 

> make[5]: Entering directory
> `/usr/home/remy/postgresql-8.2beta1/src/backend/utils/adt'
> /opt/SUNWspro/bin/cc -Xa -xtarget=ultraT1 -fast -I../../../../src/include  
> -c -o float.o float.c
> "float.c", line 112: identifier redeclared: cbrt
> current : static function(double) returning double
> previous: function(double) returning double :
> "/usr/include/iso/math_c99.h", line 126
> cc: acomp failed for float.c

You need to find out why configure failed to detect that cbrt() is
available.

regards, tom lane

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq