You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that #112 has been resolved is excellent news, thank you very much.
In this case, all what is left is to wrap up this patch for the documentation, demonstrating DBeaver with CrateDB >= 5.9.1 works well when using the vanilla pgJDBC driver? Wonderful!
May I ask if data I/O using all CrateDB special data types has been validated
Arrays --> recognised as such in reads, also work for inserts through the GUI (need to use curly brackets syntax {1,2} instead of [1,2])
Objects --> seen as string, ok to insert via GUI geo_shape --> seen as string, ok to insert via GUI geo_point --> seen as string, for insert through GUI need to use parentheses float_vector --> seen as array on read, can be inserted through GUI with same considerations as arrays
That's excellent feedback, thanks. I think it will be good to document those details on the new page educating about DBeaver (crate/cratedb-guide#157), because it can help people to get started much easier.
Hi.
that #112 has been resolved is excellent news, thank you very much.
In this case, all what is left is to wrap up this patch for the documentation, demonstrating DBeaver with CrateDB >= 5.9.1 works well when using the vanilla pgJDBC driver? Wonderful!
May I ask if data I/O using all CrateDB special data types has been validated, or does this integration only provide basic support?
With kind regards,
Andreas.
/cc @hlcianfagna, @proddata
The text was updated successfully, but these errors were encountered: