Hello,
Thanks for your response.
On Thursday 03 December 2009 16:46:54 Tom Lane wrote:
> Sam Mason 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 going to be muc
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 struggl
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,
cn_
-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
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 wrote:
> Craig Ringer wrote:
> > Kern Sibbald wrote:
> >
> >> Hello,
> >>
> >> Thanks for all the answers; I am a bit overwhelmed by t
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 o
pgsql-general@ removed from CC list:
Craig Ringer wrote:
> Come to think of it, if the fd and database are both on a utf-8
> encoding, the fd should *still* validate the utf-8 filenames it reads.
> There's no guarantee that just because the system thinks the filename
> should be utf-8, it's actua
> 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 o
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 ma
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). O
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 us
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 probabl
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 th
Hi!
On Thu, Dec 3, 2009 at 10:39 PM, 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
On 3/12/2009 11:03 AM, Tom Lane wrote:
> Craig Ringer 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 database foo lc_ct
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 bac
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
f
17 matches
Mail list logo
