...
How can I enable system catalog modifications?
Thanks for your help, so far.
Andi
Tom Lane schrieb:
Andreas Kalsch writes:
But with this operation you will recreate the whole index. - I have
found out, that the name of the constraint's index is the same as the
constraint, so th
David Fetter schrieb:
On Thu, Oct 08, 2009 at 08:24:06PM +0200, Andreas Kalsch wrote:
How do I rename constraints? Renaming columns will not rename constraints.
BEGIN;
ALTER TABLE foo DROP CONSTRAINT bar;
ALTER TABLE foo ADD CONSTRAINT bluf...;
COMMIT;
Cheers,
David.
--
Sent
How do I rename constraints? Renaming columns will not rename constraints.
Andi
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
My standard encoding is UTF-8 on all levels so I don't need this
high-cost call:
plpy.execute("select setting from pg_settings where name =
'server_encoding'");
Additionally I want to get the original cases.
For this purpose my solution is still fitting to my need. But it is not
the one you
included in
the main distribution?
Andi
Sam Mason schrieb:
On Wed, Sep 16, 2009 at 09:35:02PM +0200, Andreas Kalsch wrote:
CREATE OR REPLACE FUNCTION test (str text)
RETURNS text
AS $$
import unicodedata
return unicodedata.normalize('NFKD', str.decode('UTF
Update: The error is of course: The function tries to return "str"
instead of unicode. It is not str.decode('UTF-8') which causes the error.
Andreas Kalsch schrieb:
No,
I need a solution which is as generic as possible. I use UTF-8 encoded
unicode strings on all levels.
NSERT INTO t (ts) VALUES(to_tsvector(normalize(?)));
Andi
David Fetter schrieb:
On Wed, Sep 16, 2009 at 07:20:21PM +0200, Andreas Kalsch wrote:
Has somebody integrated Unicode normalization into Postgres? if not, I
would have to implement my own function by using this CPAN module:
h
Has somebody integrated Unicode normalization into Postgres? if not, I
would have to implement my own function by using this CPAN module:
http://search.cpan.org/~sadahiro/Unicode-Normalize-1.03/ .
I need a function which removes all diacritics (1) and transforms some
characters to a more compa
rting from exotic sets and it's the way
to go for a site with high traffic. I would prefer to do it on the
PHP/Python side to send in one encoding to the database server, because
it could be that you additionally send own strings.
Alban Hertroys schrieb:
On 4 Aug 2009, at 15:02, Andr
2009, at 24:57, Andreas Kalsch wrote:
I think the real problem is: Where do you lose the original encoding
the users input their data with? If you specify that encoding on the
connection and send it to a database that can handle UTF-8 then you
shouldn't be getting any conversion problem
Two causes:
1) I have to rewrite many lines of code = time
2) In MySQL I have access - with superuser rights - to _all_ existing
databases inside the installation. In Postgres I haven't.
But, of course, that are just details.
Best,
Andi
Tom Lane schrieb:
Andreas Kalsch writes:
gant, but will be my solution then ...
John R Pierce schrieb:
Andreas Kalsch wrote:
Will it decrease performance to refer to other schemas?
no. the schemas are simply two namespaces in the same database.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
Will it decrease performance to refer to other schemas?
David Fetter schrieb:
On Tue, Aug 04, 2009 at 04:41:51AM +0200, Andreas Kalsch wrote:
How is it possible to refer to another database, like:
select * from otherDatabase.nodes;
Generally, you use schemas for this. Schemas are
How is it possible to refer to another database, like:
select * from otherDatabase.nodes;
I have read something about schemas and I have simply created an own
schema for every database with the same name, but it still does not
work. Is there anything plain and simple?
Best,
Andi
--
Sent v
Alban Hertroys schrieb:
On 3 Aug 2009, at 20:32, Andreas Kalsch wrote:
Problem: Users will enter _any_ characters in my application and an
error really doesn't help in this case.
I think the real problem is: Where do you lose the original encoding
the users input their data with? I
So there is definitely no way to this natively? Which would be better
because this an easy task, which should be part of the main distribution.
What is more performant - has anyone made a benchmark?
1) Perl:
http://markmail.org/message/2jpp7p26ohreqnsh?q=plperlu+iconv+postgresql&page=1&refer=2
The function "convert_to(string text, dest_encoding name)" will throw an
error and so break my application when not supported characters are
included in the unicode string.
So what can I do
- to filter characters out which have no counterpart in the latin codesets
- or to simple ignore wrong cha
The function "convert_to(string text, dest_encoding name)" will throw an
error and so break my application when not supported characters are
included in the unicode string.
So what can I do
- to filter characters out which have no counterpart in the latin codesets
- or to simple ignore wrong cha
18 matches
Mail list logo
