On 4/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Problem consist of transportation data, received by SQL, into external
world. As i already wrote, it's very difficalt for users (in practice)
to use libraries of additional language (php , perl, etc) for that.
I offer to put one feature i
>In particular, XML is actually miserably bad at capturing certain kinds of
>relations between items.
Write examples, please.
P.S. By the way, XML is mentioned as tool for traffic (for transport).
But i agree to forget about that to learn what are you imply in your
quoting.
>SQL is not so fanta
May I suggest you post an EXPLAIN ANALYZE to the group for the query you're
having problems with...?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Stuart McGraw
Sent: Thursday, 19 April 2007 04:17
To: pgsql-sql@postgresql.org
Subject: [SQL] slowness whe
I have several times now run into what seems
like similar performance problems with some
of my postgresql queries.
I have a view that runs reasonably quicky.
I use this view in a subselect in another
query and that query too runs reasonably
quicky.
The view returns some unwanted duplicate
row
Does postgresql have a function that will give me
the numeric unicode code point for a character in
a unicode (aka utf8) database text string? That is,
something like ascii() but that works for unicode
characters?
---(end of broadcast)---
TIP 2: