[BUGS] BUG #2500: subscribing for digest
The following bug has been logged online:
Bug reference: 2500
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 0.0
Operating system: Unix
Description:subscribing for digest
Details:
subscribe-digest pgsql-general
The subscribe command did not succeed.
The command mode "digest" is invalid. The following command
modes, separated by hyphens ('-') or equals signs ('=') are valid:
noinform
nolog
nomessage
nowelcome
quiet
rule
set
welcome
The same with pgsql-sql
But http://archives.postgresql.org/ says I can subscribe for a digest of the
above lists.
[
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
[BUGS] BUG #2501: JOIN and capitial letters in Table Row
The following bug has been logged online: Bug reference: 2501 Logged by: ALL Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: Windows Description:JOIN and capitial letters in Table Row Details: I had a table as like the following named products: id ClientIDProductID is_multiqty is_active 1 12345 101 1 1 2 12345 102 0 1 and another table named productoptions with the following: id ProductID Sku Description OptionIDminpayments maxpayments maxqty is_acti ve 1 101 somedesc1 1 1 1 0 1 1 102 CX7535 somedesc2 1 1 3 0 1 when I ran the following sql I got: ""ERROR: column product.ProductID does not exist": SELECT * FROM products JOIN productoptions ON products.ProductID = productoptions.ProductID However, if i changed the name of the fields in the database to: "productid" It would work fine. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #2496: Troubles with fixed-point types (NUMERIC, DECIMAL,...)
Can you set "log_statement" in postgresql.conf and post the logged statements? -- With regards, William ZHANG - Original Message - From: ""Heinz-Peter Heidinger"" <[EMAIL PROTECTED]> Newsgroups: pgsql.bugs Sent: Saturday, June 24, 2006 3:44 PM Subject: BUG #2496: Troubles with fixed-point types (NUMERIC, DECIMAL,...) > > The following bug has been logged online: > > Bug reference: 2496 > Logged by: Heinz-Peter Heidinger > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.x > Operating system: all (Linux & Win was tested) > Description:Troubles with fixed-point types (NUMERIC, DECIMAL,...) > Details: > > OpenOffice 1.x/2.x & StarOffice7/..8 cannot write fixed-point values > (NUMERIC|DECIMAL) to a PGSQL database when using a JDBC interface and a > desktop locale of 'german' (maybe others as well) is used. > > > The resulting message is: > >ERROR: column has type numeric but >expression has type character varying. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: RE : [BUGS] BUG #2497: bug initdb
bruno corbin wrote: > All my system is ok but my file systeme is reiserfs > > Is-it possible that it don't works with reiserfs ? Not at all! It certainly works with Reiserfs and a ton other FSes. How do you know your system is OK? > -Message d'origine- > De : Alvaro Herrera [mailto:[EMAIL PROTECTED] > Envoyé : lundi 26 juin 2006 21:44 > À : bruno Corbin > Cc : pgsql-bugs@postgresql.org > Objet : Re: [BUGS] BUG #2497: bug initdb > > > bruno Corbin wrote: > > > copying template1 to postgres ... FATAL: could not create file > > "base/10793/1247": Input/output error > > This is a system-level error message. Probably the disk is bad, or the > cable, or the RAM, etc. See the kernel log for more information. > > -- > Alvaro Herrera > http://www.CommandPrompt.com/ > The PostgreSQL Company - Command Prompt, Inc. -- Alvaro Herrerahttp://www.PlanetPostgreSQL.org Jason Tesser: You might not have understood me or I am not understanding you. Paul Thomas: It feels like we're 2 people divided by a common language... ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #2494: SCROLL CURSOR does not worl
There's no such thing as a 'SCROLL CURSOR' in plpgsql: http://www.postgresql.org/docs/8.1/interactive/plpgsql-cursors.html I'm pretty sure that the default behavior would be scrollable. We should probably add a TODO to bring the plpgsql cursor syntax inline with what the backend supports. On Fri, Jun 23, 2006 at 01:44:24PM +, Michal Szymanski wrote: > > The following bug has been logged online: > > Bug reference: 2494 > Logged by: Michal Szymanski > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1 > Operating system: Windows > Description:SCROLL CURSOR does not worl > Details: > > Function with scroll cursor cannot be compiled. > ERROR: syntax error at or near "CURSOR" > CONTEXT: invalid type name "SCROLL CURSOR FOR SELECT * FROM freeconet.alias > WHERE mask >" > compile of PL/pgSQL function "dummy" near line 3 > > Function that I want compile. > CREATE OR REPLACE FUNCTION freeconet.dummy ( > )RETURNS INT8 AS $$ > DECLARE > rowvar freeconet.ALIAS%ROWTYPE; > DECLARE curs1 SCROLL CURSOR FOR SELECT * FROM freeconet.alias WHERE > mask>='+4850X' LIMIT 100 ; > BEGIN > BEGIN > > OPEN curs1; > FETCH curs1 INTO rowvar; > > EXCEPTION > WHEN OTHERS THEN > RAISE WARNING ' Kod bledu = %', SQLSTATE; > RETURN -1; /* blad danych */ > END; > RAISE WARNING ' mask=%',rowvar.mask; > RETURN 1; > END; > $$ LANGUAGE 'plpgsql' VOLATILE; > > ---(end of broadcast)--- > TIP 4: Have you searched our list archives? > >http://archives.postgresql.org > -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(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 #2500: subscribing for digest
Moving to -www
On Tue, Jun 27, 2006 at 06:24:34PM +, [EMAIL PROTECTED] wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2500
> Logged by:
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 0.0
> Operating system: Unix
> Description:subscribing for digest
> Details:
>
> subscribe-digest pgsql-general
> The subscribe command did not succeed.
>
> The command mode "digest" is invalid. The following command
> modes, separated by hyphens ('-') or equals signs ('=') are valid:
> noinform
> nolog
> nomessage
> nowelcome
> quiet
> rule
> set
> welcome
>
>
> The same with pgsql-sql
>
> But http://archives.postgresql.org/ says I can subscribe for a digest of the
> above lists.
> [
>
> ---(end of broadcast)---
> TIP 5: don't forget to increase your free space map settings
>
--
Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED]
Pervasive Software http://pervasive.comwork: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #2501: JOIN and capitial letters in Table Row
If you define an object using quotes to preserve case, you must always refer to that object with quotes, ie: productoptions."ProductID". My recommendation: use underscores in the database (product_options.product_id). Personally, I wouldn't pluralize the table names either, but that's just me... On Wed, Jun 28, 2006 at 03:13:28AM +, ALL wrote: > > The following bug has been logged online: > > Bug reference: 2501 > Logged by: ALL > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1 > Operating system: Windows > Description:JOIN and capitial letters in Table Row > Details: > > I had a table as like the following named products: > > idClientIDProductID is_multiqty is_active > 1 12345 101 1 1 > 2 12345 102 0 1 > > and another table named productoptions with the following: > > idProductID Sku Description OptionIDminpayments > maxpayments maxqty is_acti > ve > 1 101 somedesc1 1 1 1 0 1 > 1 102 CX7535 somedesc2 1 1 3 0 1 > > when I ran the following sql I got: ""ERROR: column product.ProductID does > not exist": > > SELECT * > FROM products > JOIN productoptions > ON products.ProductID = productoptions.ProductID > > However, if i changed the name of the fields in the database to: > > "productid" > > It would work fine. > > ---(end of broadcast)--- > TIP 2: Don't 'kill -9' the postmaster > -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(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 #2494: SCROLL CURSOR does not worl
Added to TODO: > o Add support for WITH HOLD and SCROLL cursors > > PL/pgSQL cursors should support the same syntax as > backend cursors. --- Jim C. Nasby wrote: > There's no such thing as a 'SCROLL CURSOR' in plpgsql: > http://www.postgresql.org/docs/8.1/interactive/plpgsql-cursors.html > I'm pretty sure that the default behavior would be scrollable. > > We should probably add a TODO to bring the plpgsql cursor syntax inline > with what the backend supports. > > On Fri, Jun 23, 2006 at 01:44:24PM +, Michal Szymanski wrote: > > > > The following bug has been logged online: > > > > Bug reference: 2494 > > Logged by: Michal Szymanski > > Email address: [EMAIL PROTECTED] > > PostgreSQL version: 8.1 > > Operating system: Windows > > Description:SCROLL CURSOR does not worl > > Details: > > > > Function with scroll cursor cannot be compiled. > > ERROR: syntax error at or near "CURSOR" > > CONTEXT: invalid type name "SCROLL CURSOR FOR SELECT * FROM freeconet.alias > > WHERE mask >" > > compile of PL/pgSQL function "dummy" near line 3 > > > > Function that I want compile. > > CREATE OR REPLACE FUNCTION freeconet.dummy ( > > )RETURNS INT8 AS $$ > > DECLARE > > rowvar freeconet.ALIAS%ROWTYPE; > > DECLARE curs1 SCROLL CURSOR FOR SELECT * FROM freeconet.alias WHERE > > mask>='+4850X' LIMIT 100 ; > > BEGIN > > BEGIN > > > > OPEN curs1; > > FETCH curs1 INTO rowvar; > > > > EXCEPTION > > WHEN OTHERS THEN > > RAISE WARNING ' Kod bledu = %', SQLSTATE; > > RETURN -1; /* blad danych */ > > END; > > RAISE WARNING ' mask=%',rowvar.mask; > > RETURN 1; > > END; > > $$ LANGUAGE 'plpgsql' VOLATILE; > > > > ---(end of broadcast)--- > > TIP 4: Have you searched our list archives? > > > >http://archives.postgresql.org > > > > -- > Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] > Pervasive Software http://pervasive.comwork: 512-231-6117 > vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 > > ---(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 > -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
