Hello,
Thanks for your response.
On Thursday 03 December 2009 16:46:54 Tom Lane wrote:
Sam Mason s...@samason.me.uk writes:
As others have said; BYTEA is probably the best datatype for you to
use. The encoding of BYTEA literals is a bit of a fiddle and may need
some changes, but it's
Kern Sibbald wrote:
Hello,
Thanks for all the answers; I am a bit overwhelmed by the number, so I am
going to try to answer everyone in one email.
The first thing to understand is that it is *impossible* to know what the
encoding is on the client machine (FD -- or File daemon). On say
Craig Ringer wrote:
Kern Sibbald wrote:
Hello,
Thanks for all the answers; I am a bit overwhelmed by the number, so I am
going to try to answer everyone in one email.
The first thing to understand is that it is *impossible* to know what the
encoding is on the client machine (FD -- or
Craig Ringer wrote:
Kern Sibbald wrote:
Hello,
Thanks for all the answers; I am a bit overwhelmed by the number, so I
am
going to try to answer everyone in one email.
The first thing to understand is that it is *impossible* to know what
the
encoding is on the client machine (FD -- or
On 12/3/2009 3:33 AM, Craig Ringer wrote:
Kern Sibbald wrote:
Hello,
Thanks for all the answers; I am a bit overwhelmed by the number, so I am
going to try to answer everyone in one email.
The first thing to understand is that it is *impossible* to know what the
encoding is on the client
Hi Avi
Please have a look at this link, this is how to install Bacula with MYSQL
database with Hebrew support
Eitan
On Thu, Dec 3, 2009 at 12:35 PM, Avi Rozen avi.ro...@gmail.com wrote:
Craig Ringer wrote:
Kern Sibbald wrote:
Hello,
Thanks for all the answers; I am a bit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig Ringer wrote:
Kern Sibbald wrote:
Hello,
Thanks for all the answers; I am a bit overwhelmed by the number, so I am
going to try to answer everyone in one email.
The first thing to understand is that it is *impossible* to know what the
Frank Sweetser wrote:
Unless, of course, you're at a good sized school with lots of
international students, and have fileservers holding filenames created
on desktops running in Chinese, Turkish, Russian, and other locales.
What I struggle with here is why they're not using ru_RU.UTF-8,
On 12/03/2009 10:54 AM, Craig Ringer wrote:
Frank Sweetser wrote:
Unless, of course, you're at a good sized school with lots of
international students, and have fileservers holding filenames created
on desktops running in Chinese, Turkish, Russian, and other locales.
What I struggle with
On 2/12/2009 9:18 PM, Kern Sibbald wrote:
Hello,
I am the project manager of Bacula. One of the database backends that Bacula
uses is PostgreSQL.
As a Bacula user (though I'm not on the Bacula lists), first - thanks
for all your work. It's practically eliminated all human intervention
from
On Thu, Dec 03, 2009 at 10:54:07AM +0800, Craig Ringer wrote:
Anyway, it'd be nice if Bacula would convert file names to utf-8 at the
file daemon, using the encoding of the client, for storage in a utf-8
database.
+1 for me.
this is the way to go.
I understand people with an existing backup
On 3/12/2009 11:03 AM, Tom Lane wrote:
Craig Ringercr...@postnewspapers.com.au writes:
It's a pity that attempting to specify an encoding other than the safe
one when using a non-template0 database doesn't cause the CREATE
DATABASE command to fail with an error.
Huh?
regression=# create
Hi!
On Thu, Dec 3, 2009 at 10:39 PM, Jerome Alet jerome.a...@univ-nc.nc wrote:
On Thu, Dec 03, 2009 at 10:54:07AM +0800, Craig Ringer wrote:
Anyway, it'd be nice if Bacula would convert file names to utf-8 at the
file daemon, using the encoding of the client, for storage in a utf-8
database.
On 3/12/2009 11:09 AM, Jerome Alet wrote:
On Thu, Dec 03, 2009 at 10:54:07AM +0800, Craig Ringer wrote:
Anyway, it'd be nice if Bacula would convert file names to utf-8 at the
file daemon, using the encoding of the client, for storage in a utf-8
database.
+1 for me.
this is the way to go.
Stephen Frost wrote:
* Craig Ringer (cr...@postnewspapers.com.au) wrote:
... so it's defaulting to SQL_ASCII, but actually supports utf-8 if your
systems are all in a utf-8 locale. Assuming there's some way for the
filed to find out the encoding of the director's database, it probably
Hello,
Thanks for all the answers; I am a bit overwhelmed by the number, so I am
going to try to answer everyone in one email.
The first thing to understand is that it is *impossible* to know what the
encoding is on the client machine (FD -- or File daemon). On say a
Unix/Linux system, the
16 matches
Mail list logo
