> 05.04.2016 18:24, Dimitry Sibiryakov wrote:
>>
>> In V4 will we still support connection to database on network share or
>> mapped drive
>> using the trick with overwriting "local" connection string to named pipes
>> one?
>> I.e. can expand_share_name() be cleaned out of isc_file.cpp?
>
> I'd
05.04.2016 18:46, Dmitry Yemanov wrote:
> I'd go even further and wipe out the named pipes (aka WNET) protocol
> too. I don't see any sense in it nowadays.
+many
Vlad
--
Firebird-Devel mailing list, web interface at
05.04.2016 17:46, Dmitry Yemanov wrote:
> I'd go even further and wipe out the named pipes (aka WNET) protocol
> too. I don't see any sense in it nowadays.
It has one advantage over plain TCP: no tweaking of a firewall is required.
--
WBR, SD.
05.04.2016 18:24, Dimitry Sibiryakov wrote:
>
> In V4 will we still support connection to database on network share or mapped
> drive
> using the trick with overwriting "local" connection string to named pipes one?
> I.e. can expand_share_name() be cleaned out of isc_file.cpp?
I'd go even
Hello, All.
In V4 will we still support connection to database on network share or
mapped drive
using the trick with overwriting "local" connection string to named pipes one?
I.e. can expand_share_name() be cleaned out of isc_file.cpp?
--
WBR, SD.
On 04/05/2016 05:07 PM, Wols Lists wrote:
> On 05/04/16 14:53, Alex Peshkoff wrote:
>> On 04/05/2016 04:43 PM, Dimitry Sibiryakov wrote:
>>> 05.04.2016 15:22, Alex Peshkoff wrote:
Yes currently all keys are ASCII but it's
used also for plugins configuration and I see no reasons why
On 04/05/2016 05:13 PM, Dimitry Sibiryakov wrote:
> 05.04.2016 15:53, Alex Peshkoff wrote:
>> But there are a lot of other places where NoCaseString is used. And it's
>> very efficient when case-insensitive strings are needed. It will be not
>> good to loose such class.
> Yes. But in most of
typo in c:\Program Files\Firebird\Firebird_3_0\doc\installation_readme.txt
--
Key: CORE-5187
URL: http://tracker.firebirdsql.org/browse/CORE-5187
Project: Firebird Core
Extend DPB / Connection String to specify database being it's own security one
(self-security database)
---
Key: CORE-5186
URL:
05.04.2016 15:53, Alex Peshkoff wrote:
> But there are a lot of other places where NoCaseString is used. And it's
> very efficient when case-insensitive strings are needed. It will be not
> good to loose such class.
Yes. But in most of these places using of case-insensitive string is causing
On 05/04/16 14:53, Alex Peshkoff wrote:
> On 04/05/2016 04:43 PM, Dimitry Sibiryakov wrote:
>> 05.04.2016 15:22, Alex Peshkoff wrote:
>>> Yes currently all keys are ASCII but it's
>>> used also for plugins configuration and I see no reasons why national
>>> characters can't arrive there.
>>
Connection string: to have option demanding/prohibiting use of embedded
(in-process) engine.
-
Key: CORE-5185
URL: http://tracker.firebirdsql.org/browse/CORE-5185
On 04/05/2016 04:43 PM, Dimitry Sibiryakov wrote:
> 05.04.2016 15:22, Alex Peshkoff wrote:
>> Yes currently all keys are ASCII but it's
>> used also for plugins configuration and I see no reasons why national
>> characters can't arrive there.
> Because they won't work if written in utf-8 or
05.04.2016 15:22, Alex Peshkoff wrote:
> Yes currently all keys are ASCII but it's
> used also for plugins configuration and I see no reasons why national
> characters can't arrive there.
Because they won't work if written in utf-8 or any encoding different from
current locale.
--
WBR,
On 04/05/2016 03:43 PM, Dimitry Sibiryakov wrote:
> 04.04.2016 18:13, Alex Peshkoff wrote:
>> Method 3 is good when talking about comparison
> Unfortunately it seems to be no-go because Firebird::AbstractString is
> not template but
> a class in contrast with std::string.
On top of it is
04.04.2016 18:13, Alex Peshkoff wrote:
> Method 3 is good when talking about comparison
Unfortunately it seems to be no-go because Firebird::AbstractString is not
template but
a class in contrast with std::string.
> one more related problem. We also have another
> "incarnation" of
16 matches
Mail list logo
