ksbhaskar
commented
5 years ago Thanks for bringing this need to our attention, Piotr. We'll see what we can do.
Regards – Bhaskar
On 12/24/18 10:54 PM, Piotr Koper wrote:
Please, consider reverting gtm_* symbols back. YottaDB without gtm_init and gtm_ci(p) symbols cannot be used as a replacement for embedded GT.M. If I'd like to support both GT.M and YottaDB installations as embedded databases, I have to create dynamically loaded drivers (one for GT.M, one for YottaDB - a specially compiled program with new version of gtmxc_types.h). From the user perspective there is no good reason for breaking ABI compatibility with GT.M's libgtmshr.so. In other words, the lack of ABI compatibility with GT.M's libgtmshr.so makes transition from GT.M to YottaDB harder in existing installations.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/YottaDB/YDB/issues/349, or mute the thread https://github.com/notifications/unsubscribe-auth/AAiqeuJi0oXZ0pH-JqMxd0r8UGZk6isUks5u8aFtgaJpZM4ZgyxP.
-- YottaDB - Rock solid. Lightning fast. Secure. Pick any three.
estess
nars1
Please, consider reverting gtm_* symbols back. YottaDB without gtm_init and gtm_ci(p) symbols cannot be used as a replacement for embedded GT.M. If I'd like to support both GT.M and YottaDB installations as embedded databases, I have to create dynamically loaded drivers (one for GT.M, one for YottaDB - a specially compiled program with new version of gtmxc_types.h). From the user perspective there is no good reason for breaking ABI compatibility with GT.M's libgtmshr.so. In other words, the lack of ABI compatibility with GT.M's libgtmshr.so makes transition from GT.M to YottaDB harder in existing installations.