The following bug has been logged online:
Bug reference: 3845
Logged by: Bozhan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3-beta4
Operating system: WinfowsXP
Description:tray icon that service is running
Details:
postgres needs icon in tray to show that
Tom Lane wrote:
> Michael Glaesemann <[EMAIL PROTECTED]> writes:
>> I'm probably being dense, but I don't see how this is an issue.
>
> That's just a bug in his example ;-)
Right, sorry. I meant boolean_array rather than boolean_value:
=> SELECT 'a' <> 'a' || '{true}';
?column?
--
{f,t
The following bug has been logged online:
Bug reference: 3844
Logged by: daniel birnbaum
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5-1
Operating system: windows vista
Description:will not install
Details:
when i try to install it reports a error sayin
Michael Glaesemann <[EMAIL PROTECTED]> writes:
> I'm probably being dense, but I don't see how this is an issue.
That's just a bug in his example ;-)
The real question is whether there is enough of a problem here to
justify creating new problems, in the form of backwards-compatibility
hazards. O
On Dec 29, 2007, at 14:09 , Pedro Gimeno wrote:
variants of which I think can be
relatively common compared to e.g. applications that build a boolean
array using expr1 <> expr2 || boolean_value.
I'm probably being dense, but I don't see how this is an issue. || is
string concatenation, not
Tom Lane wrote:
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
>> That said, bringing PostgreSQL into compliance with the standard
>> would undoubtedly break some people's existing applications.
I wonder how that compares to broken queries while migrating databases
from other systems. I'd bet the
