Please enable JavaScript to view this site.

Yuki Data Model

Navigation: » No topics above this level «

Provider Yuki: Online accounting.

Scroll Comments Prev Top Next More

Online accounting.

Code for use in settings.xml: Yuki

Alias: yuki

Abbreviation: yki

Status: Production

Available in Editions: Paid

String-comparison is Case-sensitive: true

Use Catalog in Full Name: true

Use Schema in Full Name: true

Partition Column: COMPANY_CODE

Technical Documentation: http://help.yuki.nl/documents/homepage/startpagina-yuki-api-documentatie

Non-technical Documentation: https://yukiworks.com

Provider Attributes

The following provider attributes are available for Yuki:

Code

Description

Default Value

Set from Connection String

Set from Set SQL-Statement

Set from Providers File

Set from Log On

api-url

URL of Yuki web service

 

 

 

bulk-delete-page-size-rows

Number of rows to delete per batch when bulk deleting

10000

 

bulk-insert-page-size-bytes

Approximate maximum size in bytes of batch when bulk inserting

10000000

 

bulk-insert-page-size-rows

Number of rows to insert per batch when bulk inserting

10000

 

force-case-sensitive-identifiers

Consider identifiers as case-sensitive independent of the platform capabilities.

False

 

forced-casing-identifiers

Forced casing of identifiers. Choose from Unset, Lower, Upper and Mixed.

 

 

http-disk-cache-compression-level

Compression level for the HTTP disk cache, ranging from 1 (little) to 9 (intense). Default is 5.

5

 

http-disk-cache-directory

Directory where HTTP cache is stored.

C:\Users\gle3\Invantive\Cache\http\gle3\shared

 

http-disk-cache-max-age-sec

Maximum acceptable age in seconds for use of data in the HTTP disk cache.

2592000

 

http-get-timeout-ms

HTTP GET timeout (ms)

300000

 

http-memory-cache-compression-level

Compression level for the HTTP memory cache, ranging from 1 (little) to 9 (intense). Default is 5.

5

 

http-memory-cache-max-age-sec

Maximum acceptableage in seconds for use of data in the HTTP memory cache.

14400

 

http-post-timeout-ms

HTTP POST timeout (ms)

300000

 

invantive-sql-forward-filters-to-data-containers

Whether to forward filters to data containers.

True

 

invantive-sql-shuffle-fetch-results-data-containers

Whether to shuffle results fetched from data containers.

False

 

invantive-use-cache

Whether to cache the results of a query.

True

 

maximum-length-identifiers

Non-default maximum length in characters of identifier names.

 

 

max-url-length-accepted

The maximum accepted URL length before raising an error.

8000

 

max-url-length-desired

The maximum desired URL length.

8000

 

partition-slot-based-rate-limit-length-ms

Total length in ms across all slots of a partition-based rate limit.

60000

 

 

partition-slot-based-rate-limit-slots

Number of slots per partition-based rate limit. Null means no slot-based rate limit

 

 

 

pre-request-delay-ms

Pre-request delay in milliseconds per request.

0

 

requests-parallel-max

Maximum number of parallel data requests from individual partitions on the data container.

32

 

result-set-cache

Action: provide 'empty' to empty.

 

 

 

 

slot-based-rate-limit-length-ms

Total length in ms across all slots of a slot-based rate limit.

60000

 

 

slot-based-rate-limit-slots

Number of slots of a slot-based rate limit. Null means no slot-based rate limit

 

 

 

standardize-identifiers

Rewrite all identifiers to the preferred standards as configured by standardize-identifiers-casing and maximum-length-identifiers.

True

 

standardize-identifiers-casing

Rewrite all identifiers to the recommended standard platform-specific casing when changing a data model on a case-dependent platform.

True

 

trace-native-calls

Trace native calls to data container backend.

False

 

use-http-disk-cache-read

Whether to use HTTP responses from previous queries stored on disk to answer the current query.

True

 

use-http-disk-cache-write

Whether to memorize HTTP responses on disk.

True

 

use-http-memory-cache-read

Whether to use HTTP responses from previous queries stored in memory to answer the current query

True

 

use-http-memory-cache-write

Whether to memorize HTTP responses in memory

True

 

use-metadata-cache

Whether to use the metadata calculated previously

Has only practical use during development on a XML provider.

True

 

use-result-cache

Whether to use result sets from previous queries that can answer the current query

True

 

 

02-12-2019 20:1617.33.216-BETA+2512