Hi Alex, >> But I would drop the database name from the first message and only mention >> the directory path, a) because that's the location, and b) for consistency >> between DatabaseAccess and ExternalFileAccess.
> Sorry, in external file access it's also filename here, I've just typed > it w/o extension. > What about removing file name - it's not too hard, but may cause > problems when using new messages file with old server, you will get some > path and to say is it directory or full file name one will have to take > server version into an account. Special bad result will be when using > old client with new server... Well, if it causes trouble then leave the filename in - in both cases. Only the message becomes a tad silly: "Use of external file at location /mnt/abc/exttable.txt is not allowed by server configuration" You could shorten it to: "Use of external file /mnt/abc/exttable.txt is not allowed by server configuration" But then you leave out an important clue: that it's the *location* that is forbidden. OTOH, "server configuration" should be enough to point the inquisitive user to the firebird.conf file. OTOOH, the version without "at location" strongly suggests that the problem is with the *file*, not the directory. So all in all, it's probably best to keep it as you have it now: 'Use of external file at location /path/to/filename.ext is not allowed by server configuration' Cheers, Paul ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
