...
Tip |
---|
Conditions for connection
|
...
Use “New Connection” to choose the database and define the connection string. ( This dialog only opens if you are logged into the server)
DBMS Driver Requirement List
Some databases may require an extra driver to be installed. Please check the list below.
Expand | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|
Alternative Connection Methods
...
The default behavior is to crawl all tables and rows.
Tables must have primaryKey by default. You may choose to index tables w/o a primary key also.
You may choose a sampling mode, as only the selected number of rows is indexed in each table.
You may choose a subset of tables.
You may limit columns by their names.
You may define SQLs to change content to be indexed
Embedded files are indexed with proper definitions
File paths are processed with proper definitions
If rows have some permission information you may utilize it with proper definitions.
When you search in GEODI, Each row is content. You may define the name and appearance of a record database or table-wise.
Trouble Shooting
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
FAQ
DB Meta
DBmeta is a way to change all behavior here by database and/or tablewise. This page contains necessary information about how DBmetas are defined.
...
Limit indexing by table or column.
Key | Description |
---|---|
WorkspaceName | WorkSpace(s) to which the settings will apply. |
TableFilter | Tables to which the settings will apply. |
ColumnFilter | Tables that contain the given columns (if - is given, tables that do not contain the relevant columns are considered). If more than one is given, the relationship is AND. |
Code Block | ||
---|---|---|
| ||
{ "Defines":[ { "__type":"Geodi.Database.Meta.DBView, Geodi.Database", "WorkspaceName":"0000-Promotional and Educational Videos", "TableFilter":"*", "ColumnFilter":"*", "Columns":"-FILEPATH,-ID,DATE,GEODIFILELINK" }, ] } |
...
File1 column shows file names File2 column shows blob files. In the created database, the BLOB file column is selected as "bytea" data type.
You can use it in Access,Postgres,Mssql,Oracle,Sqlıte,MySql databases.
FileMemoColumn
in VT must have a file extension in the given column.If there is no extension in the column value and all files are of the same type, an extension can be added to the macro value.
Key | Description |
---|---|
| BLOB/MEMO field containing the file content. GEODI will automatically determine the file content |
| Macro for the unique number of the file. The rules for macros are at the end of the document. |
| Macro for the name of the file to appear in searches and viewers. Rules for macros are at the end of the document. |
Code Block | ||
---|---|---|
| ||
{ "Defines":[ { "__type":"Geodi.Database.Meta.DBSubContent, Geodi.Database", "TableFilter":"TEST", "IDColumnMacro":"[OBJECTID]", "FileNameColumnMacro":"[FILE1]", "FileMemoColumn":"file2" } ] } |
...
You can also index files specified by file links in a record. (CSV files are not supported).
Key | Description |
---|---|
| A macro that calculates the directories where files are located. This macro can be the value directly in a field (e.g. PATH), or it can be a path calculated in combination with other fields of the record.( Example: column name PATH on VT) |
| If there is more than one file in the file path, you can give the bracket character this way. |
Code Block | ||
---|---|---|
| ||
{ "Defines":[ { "__type":"Geodi.Database.Meta.DBSubContent, Geodi.Database", "FileFullPathColumnMacro":"[PATH]", "FileFullPathColumnSplitter":"|" } ] } |
...