On Wed, Apr 06, 2016 at 07:47:00PM +0300, Dmitry Yemanov wrote:
> 06.04.2016 19:00, Jim Starkey wrote:
>
> > I suggest that FB4 get completely out of the business of passing
> > database file names over the API and go strictly with something like a
> > URL that identifies the location and name of
On 4/6/2016 12:47 PM, Dmitry Yemanov wrote:
> 06.04.2016 19:00, Jim Starkey wrote:
>
>> I suggest that FB4 get completely out of the business of passing
>> database file names over the API and go strictly with something like a
>> URL that identifies the location and name of a database, letting the
06.04.2016 19:00, Jim Starkey wrote:
> I suggest that FB4 get completely out of the business of passing
> database file names over the API and go strictly with something like a
> URL that identifies the location and name of a database, letting the
> server configuration map the name into a file
06.04.2016 18:00, Jim Starkey wrote:
> Probably most
> of the code is already there and functional, so the exercise should be
> more dropping the interpretation of connection string as file name,
> aided by a client side back to map legacy connection strings into URLs..
Yes, most of the code
With some remorse, I recently realized that the PathName class and file
name matching is my fault as is the larger problem of a client
identifying a database by filename. It has never worked well, and if
pushed, works badly. File names are excellent for opening files and bad
almost anything
