On 01/06/13 12:29, John R Pierce wrote:
On 5/31/2013 4:29 PM, Gerald Luger wrote:
Shouldn't I expect all results to be 000...0001?
Otherwise it would be
1 != 1?
SQL's BIT type is big endian, a hangover from its IBM mainframe heritage.
I don't think it has anything to do with byte sex (I
On 01/06/13 13:01, Gavin Flower wrote:
On 01/06/13 12:29, John R Pierce wrote:
On 5/31/2013 4:29 PM, Gerald Luger wrote:
Shouldn't I expect all results to be 000...0001?
Otherwise it would be
1 != 1?
SQL's BIT type is big endian, a hangover from its IBM mainframe
heritage.
I don't
On 09/05/13 01:07, andras.va...@zalando.de wrote:
The following bug has been logged on the website:
Bug reference: 8141
Logged by: Andras Vaczi
Email address: andras.va...@zalando.de
PostgreSQL version: 9.1.9
Operating system: linux/Ubuntu 12.10
Description:
Consider the
On 26/03/13 22:06, webad...@aldar.com wrote:
The following bug has been logged on the website:
Bug reference: 7998
Logged by: Web Admin
Email address: webad...@aldar.com
PostgreSQL version: Unsupported/Unknown
Operating system: Linux
Description:
Dear Support,
We have
On 05/12/12 19:49, JEHAD GHAREEB wrote:
Hi all,
I want to install PG 7.3.4 on Linux 6 . So please send all
instructions to complete installation .
Your prompt response is highly appreciated .
Regards,
Jehad G.
Requesting information is not a bug. If you need further help, then you
might
On 18/11/12 15:46, Stephen Frost wrote:
* Phil Sorber (p...@omniti.com) wrote:
In addition it actually works!
Only until the ORM tries to create two tables that are identical except
for the last few characters..
So I am sharing this with the list to see what people think. Is this a
On 18/11/12 16:49, Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
NOTICE: identifier
this_is_a_really_long_identifier_for_a_prepared_statement_name_ok
will be truncated to
this_is_a_really_long_identifier_for_a_prepared_statement_name_
PREPARE
...
The ORM
On 18/11/12 17:10, Phil Sorber wrote:
On Nov 17, 2012 11:06 PM, Gavin Flower
gavinflo...@archidevsys.co.nz mailto:gavinflo...@archidevsys.co.nz
wrote:
On 18/11/12 16:49, Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
NOTICE: identifier
On 01/09/12 18:40, Simon Riggs wrote:
On 4 October 2011 02:42, Seiko Ishida v-sei...@microsoft.com wrote:
The following bug has been logged online:
Bug reference: 6239
Logged by: Seiko Ishida
Email address: v-sei...@microsoft.com
PostgreSQL version: 8.2.4
Operating system:
On 22/04/12 05:49, Tom Lane wrote:
eshkin...@gmail.com writes:
set timezone to 'W-SU'; select '2011-03-27 23:00:00'::timestamptz;
SET
timestamptz
2011-03-28 02:59:54+04
Bizarre. On my Fedora 16 box, I see a different misbehavior:
regression=# set timezone
On 29/03/12 12:36, Kasper Sandberg wrote:
Yeah I will try provide a patch.
I am not entirely certain how the wording should be, but I only
understood that the cube based aproach is by default in meters after
testing it out, though now of course it occurs to me that of course it
is, given the
On 28/12/11 10:43, Phil Sorber wrote:
On Tue, Dec 27, 2011 at 1:00 PM, Tom Lanet...@sss.pgh.pa.us wrote:
Phil Sorberp...@omniti.com writes:
My search foo failed me. Someone just pointed me to a similar
conversation from some months ago:
On 28/10/11 08:53, Tom Lane wrote:
Gavin Flowergavinflo...@archidevsys.co.nz writes:
Actually, a minute is not always 60 seconds, as you can legally have 62
seconds in a minute!
pedantry
There never have been, and will never be, two leap seconds declared in
the same minute --- the need for
On 28/10/11 02:13, Heikki Linnakangas wrote:
On 27.10.2011 15:57, Robert Young wrote:
But,I think insistence of hard-coding should be even worse than broken
configuration.
And hard-coding should never be a good work ethics of a professional
programmer.
You're exaggerating. There's nothing
On 23/09/11 10:43, Gavin Flower wrote:
On a LInux 64 biut system:
$ psql
psql (9.1.0)
Type help for help.
gavin= DROP TYPE raindow;
ERROR: type raindow does not exist
gavin= CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow',
'green', 'blue', 'purple');
ERROR: type rainbow already
On a LInux 64 biut system:
$ psql
psql (9.1.0)
Type help for help.
gavin= DROP TYPE raindow;
ERROR: type raindow does not exist
gavin= CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green',
'blue', 'purple');
ERROR: type rainbow already exists
gavin=
--
Sent via pgsql-bugs
On 16/07/11 05:21, Tom Lane wrote:
Gavin Flowergavinflo...@archidevsys.co.nz writes:
On 15/07/11 11:25, Gavin Flower wrote:
I think it should be possible to put a constraint on the master table
to prevent rows being inserted.
Of course, minutes after I sent the above - I realized
On 15/07/11 08:00, Gavin Flower wrote:
On 15/07/11 07:14, Tom Lane wrote:
Alvaro Herreraalvhe...@commandprompt.com writes:
Excerpts from Gavin Flower's message of jue jul 14 07:45:00 -0400 2011:
Using pg 9.1beta3, I was found that running a function generated an
error relating to escaped
On 15/07/11 11:25, Gavin Flower wrote:
On 15/07/11 08:00, Gavin Flower wrote:
On 15/07/11 07:14, Tom Lane wrote:
Alvaro Herreraalvhe...@commandprompt.com writes:
Excerpts from Gavin Flower's message of jue jul 14 07:45:00 -0400
2011:
Using pg 9.1beta3, I was found that running a function
Hi,
Using pg 9.1beta3, I was found that running a function generated an
error relating to escaped single quotes, yet still produced the answer I
expected!
/// part000.sql script ///
DROP TABLE IF EXISTS measurement CASCADE;
CREATE TABLE measurement
(
city_id int not
On 15/07/11 07:14, Tom Lane wrote:
Alvaro Herreraalvhe...@commandprompt.com writes:
Excerpts from Gavin Flower's message of jue jul 14 07:45:00 -0400 2011:
Using pg 9.1beta3, I was found that running a function generated an
error relating to escaped single quotes, yet still produced the
The following bug has been logged online:
Bug reference: 6095
Logged by: Gavin Flower
Email address: gavin.flo...@archidevsys.co.nz
PostgreSQL version: 9.1beta2
Operating system: x86_64 Linux
Description:Misleading error message: INSERT has more expressions
than
On 09/04/11 02:42, Tom Lane wrote:
Gavin Flowergavinflo...@archidevsys.co.nz writes:
I found were RETURNING is defined, so I was confused...
...
However, may be it would still be good to mention it on the SELECT page?
It is mentioned --- the subsection on the WITH clause points out that
you
On 08/04/11 21:22, Gavin Flower wrote:
On 08/04/11 14:57, Tom Lane wrote:
Gavin Flowergavin.flo...@archidevsys.co.nz writes:
I think the documentation of SELECT should include the keyword 'RETURNING'
in its synopsis.
Huh? There's no SELECT RETURNING.
regards, tom
On 08/04/11 14:57, Tom Lane wrote:
Gavin Flowergavin.flo...@archidevsys.co.nz writes:
I think the documentation of SELECT should include the keyword 'RETURNING'
in its synopsis.
Huh? There's no SELECT RETURNING.
regards, tom lane
The 'WITH' clause is described in the
The following bug has been logged online:
Bug reference: 5968
Logged by: Gavin Flower
Email address: gavin.flo...@archidevsys.co.nz
PostgreSQL version: 9.1aplha5
Operating system: x86_64 Linux
Description:DOCUMENTATION: SELECT synopsis omits RETURNING keyword
Details
The following bug has been logged online:
Bug reference: 5963
Logged by: Gavin Flower
Email address: gavin.flo...@archidevsys.co.nz
PostgreSQL version: 9.1alpha5
Operating system: x86_64 Linux
Description:make -j4 check fails
Details:
After executing
time -j4
27 matches
Mail list logo
