Hi - I noticed behaviour that I found a little curious while playing around
with named pipe connections using Firebird 3.0.3.
If you set RemoteServicePort to a non-default value, eg 3051, then the default
service name is still used for named pipe connections, eg localhost@gds_db.
You can also s
Hello Mark,
Tuesday, October 30, 2018, 8:20:51 AM, you wrote:
> On 29-10-2018 02:06, Helen Borrie hele...@iinet.net.au
> [firebird-support] wrote:
>> Character set NONE is a bare-bones ASCII set and does not provide
>> intrinsic support for any characters beyond the 128 characters that
>> provid
On 29-10-2018 21:21, sboyd...@gmail.com [firebird-support] wrote:
> So what you and Helen are telling me is that I should change the
> database to use UTF8. Correct?
Well, if your application uses UTF8, then probably yes, but if you only
need a region specific character set, then using that char
On 29-10-2018 02:06, Helen Borrie hele...@iinet.net.au
[firebird-support] wrote:
> Character set NONE is a bare-bones ASCII set and does not provide
> intrinsic support for any characters beyond the 128 characters that
> provide the US-Ascii upper and lower case, numerals and the basic
> diacritic
Steve Boyd wrote:
> I have a database that is configured with CharSet = None.
> My clients access it with CharSet = UTF8. I would not actually have
> know this if I hadn't started digging into this problem. My
> assumption was always that the clients were CharSet = None but
> something in the
On 27-10-2018 20:36, sboyd...@gmail.com [firebird-support] wrote:
> I have a database that is configured with CharSet = None.
And there is your problem: don't use NONE.
Not related to your problem, but why are you still using Firebird 2.5.1?
A lot of bugs have been fixed since 2.5.1, including a
