>> to change few aliases and don't touch application :
>>
>> year2015 = D:\archive\databases\year2015.fdb
>> year2016 = D:\archive\databases\year2016.fdb
>>
>I didn't say it would work for everyone or every situation. Does anything?
>However, as with everything else in my programs, I would have
Woody,
> >> However, it would be useful, IMO, to have an alias for directories so
> >> that conceptually, you could separate entire functionalities. For
> >> instance, the main databases reside in an alias directory called
> >> MainDataDir. Backups could be performed to the BackupDataDir.
> >
> >
From: "Vlad Khorsun"
>>
>> However, it would be useful, IMO, to have an alias for directories so
>> that
>> conceptually, you could separate entire functionalities. For instance,
>> the
>> main databases reside in an alias directory called MainDataDir. Backups
>> could be performed to the Backu
> From: "Vlad Khorsun"
>>
>>What are you going to do, when databases will overflow this single
>> directory ? Buy new HDD ? Create new
>> directory and teach application to look for databases at two
>> "superaliases" ?
>>
>
> As you pointed out, I can create a database for each year for the
From: "Dimitry Sibiryakov"
> 15.04.2011 15:08, Woody wrote:
>> However, it would be useful, IMO, to have an alias for directories so
>> that
>> conceptually, you could separate entire functionalities. For instance,
>> the
>> main databases reside in an alias directory called MainDataDir. Backups
15.04.2011 15:08, Woody wrote:
> However, it would be useful, IMO, to have an alias for directories so that
> conceptually, you could separate entire functionalities. For instance, the
> main databases reside in an alias directory called MainDataDir. Backups
> could be performed to the BackupDataDi
From: "Vlad Khorsun"
>
>What are you going to do, when databases will overflow this single
> directory ? Buy new HDD ? Create new
> directory and teach application to look for databases at two
> "superaliases" ?
>
As you pointed out, I can create a database for each year for the next
hundr
From: "Alex Peshkoff"
> If you have
> DatabaseAccess = Restrict /some/path
> in firebird.conf, each connection to server:database.fdb (when
> database.fdb is not found in aliases.conf) will expand to
> server:/some/path/database.fdb.
>
> What about exactly what you want - worth thinking on my min
On 04/15/11 14:17, Helen Borrie wrote:
> Alex,
>
> At 09:32 PM 15/04/2011, Alex Peshkoff wrote:
>
>> If you have
>> DatabaseAccess = Restrict /some/path
>> in firebird.conf, each connection to server:database.fdb (when
>> database.fdb is not found in aliases.conf) will expand to
>> server:/some/pa
> Just curious, has there been any discussion about expanding aliases to allow
> defining just a path to a directory
> where multiple database reside?
>
> The reason I'm asking is that in some situations, my apps are designed to
> allow the users to archive fiscal data.
> In general, they have
Alex,
At 09:32 PM 15/04/2011, Alex Peshkoff wrote:
>If you have
>DatabaseAccess = Restrict /some/path
>in firebird.conf, each connection to server:database.fdb (when
>database.fdb is not found in aliases.conf) will expand to
>server:/some/path/database.fdb.
>
>What about exactly what you want - w
On 03/17/11 18:29, Woody wrote:
> Just curious, has there been any discussion about expanding aliases to allow
> defining just a path to a directory where multiple database reside?
>
> The reason I'm asking is that in some situations, my apps are designed to
> allow the users to archive fiscal d
Just curious, has there been any discussion about expanding aliases to allow
defining just a path to a directory where multiple database reside?
The reason I'm asking is that in some situations, my apps are designed to allow
the users to archive fiscal data. In general, they have a main database
13 matches
Mail list logo
