Identified in:
v4.2.0/2 - Nested calls to Gqvc.LogEvent, Gqvc.CreateDirectory
Calling Gqvc.LogEvent or Gqvc.CreateDirectory through other routines, was over-writing v.ResolvedDirectoryPath value in Gqvc.ResolvePath. This led to wrong directory path being used by all referencing routines.
E.g.: Call to Gqvc.StoreDataQvd to store an in-memory table to non-existing directory would end-up storing the qvd to current directory.
SyedMaqsood
commented
9 years ago
Identified in: v4.2.0/2 - Nested calls to Gqvc.LogEvent, Gqvc.CreateDirectory
Calling Gqvc.LogEvent or Gqvc.CreateDirectory through other routines, was over-writing v.ResolvedDirectoryPath value in Gqvc.ResolvePath. This led to wrong directory path being used by all referencing routines. E.g.: Call to Gqvc.StoreDataQvd to store an in-memory table to non-existing directory would end-up storing the qvd to current directory.