TreeProjects 2.5 adds database encryption
< Next Topic | Back to topic list | Previous Topic >
Posted by Alexander Deliyannis
May 15, 2012 at 09:44 PM
Yaroslav Pidstryhach wrote:
>Even with an underlying SQL engine, there are many corner cases to think
>about.
Thanks for the feedback; indeed, I had not considered such borderline issues.
In any case, if you want suggestions for the software’s preferable behaviour, you’ve come to the right place :-)
Posted by Yaroslav Pidstryhach
May 16, 2012 at 02:08 PM
I would very much like suggestions about this feature.
Alexander Deliyannis wrote:
>In any case, if you want suggestions for the
>software’s preferable behaviour, you’ve come to the right place :-)
Posted by Alexander Deliyannis
May 18, 2012 at 07:05 AM
Yaroslav Pidstryhach wrote:
>I would very much like suggestions about this feature.
My own preferred approach when combining/importing databases from different formats (or, as in this case, different arrangements of fields) is to provide some option for ‘mapping’ fields from one format to the other. I don’t expect the software to be able to guess what corresponds with what.
The second option for me would be for the end result to include all custom fields, i.e. a/b/c/x/y/z, so I can then decide what to keep and adjust it manually.
Last, some Query By Example (QBE) tool could be useful for facilitating the automatic updating of fields, but I would only put this in the long term wish list.