Hi Listers,
I want to insert some german specific characters (umlaut characters) into a
table, but I am getting the following
Error message:
postgres=# EXECUTE stmt (1, 1 , 1 , 'Grün') ;
ERROR: invalid UTF-8 byte sequence detected near byte 0xfc
Or
postgres=# EXECUTE stmt (1, 1 , 1 , 'MAß
On Thu, Jun 15, 2006 at 01:01:56PM +0200, Milen Kulev wrote:
> postgres=# EXECUTE stmt (1, 1 , 1 , 'Grün') ;
> ERROR: invalid UTF-8 byte sequence detected near byte 0xfc
>
> Or
>
> postgres=# EXECUTE stmt (1, 1 , 1 , 'MAßßtab') ;
> ERROR: invalid UTF-8 byte sequence detected near byte 0xdf
On Jun 15 01:01, Milen Kulev wrote:
> I want to insert some german specific characters (umlaut characters)
> into a table, but I am getting the following
> Error message:
> postgres=# EXECUTE stmt (1, 1 , 1 , 'Grün') ;
> ERROR: invalid UTF-8 byte sequence detected near byte 0xfc
> ...
> postgr
Hi Thomas,
What actually the compile option --enable-recode is doing ?
I haven't compiled PG with this option for sure (perhaps is the option
On by defalt ?), but oyu advice hepled me:
postgres=# \encoding
UTF8
postgres=# \encoding
UTF8
postgres=# SET client_encoding = 'LATIN1';
SET
postgres=# \e
Hi Milen,
Milen Kulev wrote:
> Hi Listers,
> I want to insert some german specific characters (umlaut characters) into a
> table, but I am getting the following
> Error message:
> postgres=# EXECUTE stmt (1, 1 , 1 , 'Grün') ;
> ERROR: invalid UTF-8 byte sequence detected near byte 0xfc
>
>
Hi Milen,
Milen Kulev wrote:
> What actually the compile option --enable-recode is doing ?
IIRC it enables the support for string recoding, but this might not be
correct anymore ...
> I haven't compiled PG with this option for sure (perhaps is the option
> On by defalt ?), but oyu advice hepled
Thomas Beutin <[EMAIL PROTECTED]> writes:
> Milen Kulev wrote:
>> What actually the compile option --enable-recode is doing ?
> IIRC it enables the support for string recoding, but this might not be
> correct anymore ...
--enable-recode has been gone for a long time (a quick look shows it was
la
I'm running PostgreSQL 8.1.3. In my postgresql.conf, the following
works:
listen_addresses = '*'
but the following does not:
listen_addresses = '192.168.1.33'
I get an error:
WARNING: could not create listen socket for "192.168.1.33"
FATAL: could not create any TCP/IP sockets
I
On Thu, Jun 15, 2006 at 10:05:26AM -0400, Geoffrey Knauth wrote:
> I get an error:
>WARNING: could not create listen socket for "192.168.1.33"
>FATAL: could not create any TCP/IP sockets
>
> I'm running Mac OS X 10.4.6 on PPC, if that makes a difference.
Well, do you actually have an in
Geoffrey Knauth <[EMAIL PROTECTED]> writes:
> I'm running PostgreSQL 8.1.3. In my postgresql.conf, the following
> works:
> listen_addresses = '*'
> but the following does not:
> listen_addresses = '192.168.1.33'
> I get an error:
> WARNING: could not create listen socket for "192
in PHP for example, where there are multiple sessions and which you get is random:how do you know if the session you're in has prepared a particular statement?and/or how do you get a list of prepared statements?last, is there any after login trigger that one could use to prepare statements the sess
Hello,
Db-encoding LATIN1 works fine for me with german, scandic, other umlauted or
accented and even cyrillic characters.
BR,
Aarni
On Thursday 15 June 2006 14:01, Milen Kulev wrote:
> Hi Listers,
> I want to insert some german specific characters (umlaut characters) into a
> table, but I am
i frequently join certain tables together in various
tables.
view the following link for an example:
http://www.rafb.net/paste/results/mBvzn950.html
is it a good practice to leave this included in the
queries, as is, or should i factor it out somehow? if
i should factor it, how do i do so?
tia
On Thu, Jun 15, 2006 at 01:59:22PM -0700, [EMAIL PROTECTED] wrote:
>
> is it a good practice to leave this included in the
> queries, as is, or should i factor it out somehow? if
> i should factor it, how do i do so?
If what you're saying is that these additional criteria are
redundant, then it'
On Thu, 2006-06-15 at 13:59 -0700, [EMAIL PROTECTED] wrote:
> i frequently join certain tables together in various
> tables.
> is it a good practice to leave this included in the
> queries, as is, or should i factor it out somehow? if
> i should factor it, how do i do so?
Future proofing selects
On Jun 16, 2006, at 5:59 , <[EMAIL PROTECTED]> wrote:
i frequently join certain tables together in various
tables.
view the following link for an example:
http://www.rafb.net/paste/results/mBvzn950.html
is it a good practice to leave this included in the
queries, as is, or should i factor it
>
> On Jun 16, 2006, at 5:59 ,
> <[EMAIL PROTECTED]> wrote:
>
> > i frequently join certain tables together in
> various
> > tables.
> >
> > view the following link for an example:
> >
> > http://www.rafb.net/paste/results/mBvzn950.html
> >
> > is it a good practice to leave this included in
> th
> On Thu, Jun 15, 2006 at 01:59:22PM -0700,
> [EMAIL PROTECTED] wrote:
> >
> > is it a good practice to leave this included in
> the
> > queries, as is, or should i factor it out somehow?
> if
> > i should factor it, how do i do so?
>
> If what you're saying is that these additional
> criteria a
[Please quote responsibly. There was no need to quote my entire
message back to the list.]
On Jun 16, 2006, at 7:15 , <[EMAIL PROTECTED]> wrote:
i need to become mor familiar with views. if i use
views, will i substantially impair performance?
Short answer: maybe, maybe not
Long answer: b
Hi,
This is prompted by the previous thread on "SQL Technique Question". I
have the following query, extracted from a PHP script, where $dt is a
date provided to the script.
SELECT created, topic_id, 0, 0, 0, 0 FROM topic
WHERE created >= $dt AND page_type IN (1, 2)
UNION
SELEC
Each of your queries has the filter xxx >= $dt where the xxx is the first column in each select. You could simplify the query by turning the unioned selects into a sub-query and then putting the $dt filter in the outer query.
I don't know if this will cause performance problems though. If Postgre
Tom,
I omitted the LOG and HINT lines before.
LOG: could not bind IPv4 socket: Can't assign requested address
HINT: Is another postmaster already running on port 5432? If not,
wait a few seconds and retry.
WARNING: could not create listen socket for "192.168.1.33"
FATAL: could not create
Geoffrey Knauth <[EMAIL PROTECTED]> writes:
> Andrew Sullivan wrote:
>> Well, do you actually have an interface with that address?
> I think I do, in that the machine's wireless interface is set up with
> a 192.168.1.x/24 address and 1.33 is on the same subnet. Or maybe
> I'm misunderstanding
Hi Geoff,
Listen_addresses means what local interface to listen to connections - ie,
if you have 2 network interfaces (cards) in the machine that go to 2
different networks - such as one to the internet and one to your LAN, you
could tell Postgres to only listen on the LAN interface for connection
quote:
"The right way to limit incoming connections to only come *from*
particular IP addresses is to use pg_hba.conf."
Apologies Geoff - that would be the easier way rather than ipchains /
iptables.
-p
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of T
"Phillip Smith" <[EMAIL PROTECTED]> writes:
>
> I've just installed Postgres 8.1 on RedHat 7.1
Uh ... *why*? I wouldn't use RH 7.1 today any more than I'd use PG 7.1 ...
> and I'm getting the error:
> "2006-06-16 14:49:00 NZST @ []LOG: could not create IPv6 socket: Address
> family not support
Dang - Our NZ operations are a lot smaller than ours. They only have the one
Linux server and it's primary role is to run the D3 gear I was talking about
the other day - same in Australia!! I am trying to get the number crunchers
to fork out the $$$ for RH ES4 and a nice new server.
Thanks Tom, I'
Dear group, Let me explain my issue. We use Database - postgresql-8.1 JDBC Driver - postgresql-8.1-407.jdbc3.jar Java - jdk1.5 The default transaction isolation level is - Read Committed
Auto Commit is fals
sathish kumar shanmugavelu wrote:
INSERT INTO rcp_patient_visit_monitor (
entry_no, patient_id, visit_date, is_newpatient,
visit_type, is_medical,
is_review, is_labtest, is_scan, is_scopy, is_xray,
weight, height)
VALUES ((SELECT c
29 matches
Mail list logo
