|
| 1 | +(dbeaver)= |
| 2 | +# DBeaver |
| 3 | + |
| 4 | +:::{include} /_include/links.md |
| 5 | +::: |
| 6 | + |
| 7 | +```{div} |
| 8 | +:style: "float: right; margin-left: 0.5em" |
| 9 | +[{w=120px}](https://dbeaver.io/) |
| 10 | +``` |
| 11 | + |
| 12 | +[DBeaver] is a multipurpose cross-platform database tool for developers, |
| 13 | +database administrators, analysts, and everyone working with data. |
| 14 | + |
| 15 | +It is available as an open-source version _DBeaver Community_ and |
| 16 | +as a commercial version _DBeaver PRO_. |
| 17 | + |
| 18 | + |
| 19 | +## Connect |
| 20 | + |
| 21 | +::::{grid} 2 |
| 22 | + |
| 23 | +:::{grid-item} |
| 24 | +:columns: 7 |
| 25 | +Please specify database URL and credentials of your CrateDB cluster. |
| 26 | +For connecting to CrateDB, the standard [PostgreSQL JDBC Driver] |
| 27 | +will be used. |
| 28 | + |
| 29 | +When connecting to [CrateDB Self-Managed] on localhost, |
| 30 | +for evaluation purposes, use: |
| 31 | +``` |
| 32 | +jdbc:postgresql://localhost:5432/crate |
| 33 | +``` |
| 34 | + |
| 35 | +When connecting to [CrateDB Cloud], use: |
| 36 | +``` |
| 37 | +jdbc:postgresql://<clustername>.cratedb.net:5432/crate |
| 38 | +``` |
| 39 | +::: |
| 40 | +:::{grid-item} |
| 41 | +:columns: 5 |
| 42 | +{w=480px} |
| 43 | +::: |
| 44 | + |
| 45 | +:::: |
| 46 | + |
| 47 | + |
| 48 | +## Usage |
| 49 | +Use the tree menu on the left-hand pane to navigate to the `doc` schema and |
| 50 | +its tables. Navigate to the Data tab to browse your table data. |
| 51 | + |
| 52 | +{h=240px} |
| 53 | +{h=240px} |
| 54 | + |
| 55 | + |
| 56 | +## Learn |
| 57 | + |
| 58 | +:::{rubric} Tutorials |
| 59 | +::: |
| 60 | +- [Blog: Use CrateDB With DBeaver] |
| 61 | + |
| 62 | +:::{rubric} Product |
| 63 | +::: |
| 64 | +- [CrateDB and DBeaver] |
| 65 | + |
| 66 | +:::{rubric} Notes |
| 67 | +::: |
| 68 | +:::{note} |
| 69 | +A few data types of CrateDB need special considerations. |
| 70 | +- `ARRAY` types are recognised as such in reads, also work for inserts through the GUI. |
| 71 | + They need to use curly brackets syntax `{1,2}` instead of `[1,2]`. |
| 72 | +- `OBJECT` types are seen as string, and are ok to insert via GUI. |
| 73 | +- `GEO_POINT` types are seen as `STRING`, for insert through GUI, please use parentheses. |
| 74 | +- `GEO_SHAPE` types are seen as `STRING`, are ok to insert via GUI. |
| 75 | +- `FLOAT_VECTOR` types are seen as `ARRAY` on read, and can be inserted |
| 76 | + using the GUI with same considerations as `ARRAY`s. |
| 77 | +::: |
| 78 | +:::{note} |
| 79 | +We are tracking interoperability issues per [Tool: DBeaver], and appreciate |
| 80 | +any contributions and reports. |
| 81 | +::: |
| 82 | + |
| 83 | + |
| 84 | +[Blog: Use CrateDB With DBeaver]: https://cratedb.com/blog/cratedb-dbeaver |
| 85 | +[CrateDB and DBeaver]: https://cratedb.com/integrations/cratedb-and-dbeaver |
| 86 | +[DBeaver]: https://dbeaver.io/ |
| 87 | +[Tool: DBeaver]: https://github.com/crate/crate/labels/tool%3A%20DBeaver |
0 commit comments