On 4/7/2016 11:12 AM, Dimitry Sibiryakov wrote:
> 14.03.2016 10:13, Alex Peshkoff wrote:
>> There is a least one reason why expansion is needed (I have no idea how
>> can it be avoided) in yvalve. "Providers" config parameter is
>> per-database configurable, i.e. to have correct list of providers y
07.04.2016 17:22, Alex Peshkoff wrote:
> I do not remember. That code was written not by me, I just changed it a
> little when moved all kinds of expansion into single function. I've
> tried my best to keep existing logic. Found any problems with it?
You, actually, inverted logic in this part.
On 04/07/2016 06:12 PM, Dimitry Sibiryakov wrote:
> 14.03.2016 10:13, Alex Peshkoff wrote:
>> There is a least one reason why expansion is needed (I have no idea how
>> can it be avoided) in yvalve. "Providers" config parameter is
>> per-database configurable, i.e. to have correct list of providers
14.03.2016 10:13, Alex Peshkoff wrote:
> There is a least one reason why expansion is needed (I have no idea how
> can it be avoided) in yvalve. "Providers" config parameter is
> per-database configurable, i.e. to have correct list of providers yvalve
> needs to load database specific configuration
On 03/13/2016 06:42 PM, Dimitry Sibiryakov wrote:
> Hello, All.
>
> Should be allowed to use non-local path in alias expansion? I.e.
>
> local_database=remote_server:real_database
>
> If yes, alias expansion belongs to Y-valve, if not - to the engine.
>
There is a least one reason why
Hello, All.
Should be allowed to use non-local path in alias expansion? I.e.
local_database=remote_server:real_database
If yes, alias expansion belongs to Y-valve, if not - to the engine.
--
WBR, SD.
--
Tr
