Devart Forums

Adding it in code gives me this: What is the correct way of using 'WireCompression'? I looked for it in the help file but no luck, yet 'History.html' shows it added in 7.1.3.

Thank you for the information. We will investigate this UniDAC behavior and let you know the result.

We have already fixed this issue, the fix will be included in the next UniDAC build, which we are planning to release within a week.
To enable WireCompression on the client side, you will add the string "WireCompression=true" to the TUniConnection.SpecificOptions.Values['Params']. For example: In order for compression to work correctly, you should use the zlib1.dll library, the bitness of which should correspond to the bitness of your application. Please place the required zlib1.dll library in the directory with your executable file and make sure that your application starts useing it when calling the TUniConnection.Connect method.
Note, in order to determine whether your application uses zlib1.dll you can use a third-party utility, e.g. Process Explorer.

Will this also be added to IBDAC?

It already works in IBDAC.
To enable WireCompression on the client side, you should add the string "WireCompression=true" to the IBCConnection.Params. For example:

Thank you.

Is there a list of possible params which I can use with Params property? The dokumentation about this in incomplete.

Thanks, this works in the latest release but I still can't see it in the Help file.

frickler wrote: ↑Mon 21 Jan 2019 10:24 Thank you.

Is there a list of possible params which I can use with Params property? The dokumentation about this in incomplete.

Get information on using the TIBCConnection.Params property in IBDAC help: [url]https://devart.com/ibdac/docs/deva ... params.htm[/url].
The following options are currently supported:
cdd_pathname, allocation, journal, page_size, num_buffers, buffer_length, debug, garbage_collect, verify, sweep, enable_journal, disable_journal,
dbkey_scope, number_of_users, trace, no_garbage_collect, damaged, license, sys_user_name, encrypt_key, activate_shadow, sweep_interval,
delete_shadow, force_write, begin_log, quit_log, no_reserve, user_name, password, password_enc, sys_user_name_enc, interp, online_dump, old_file_size,
old_num_files, old_file_name, old_start_page, old_start_seqno, old_start_file, drop_walfile, old_dump_id, wal_backup_dir, wal_chkptlen,
wal_numbufs, wal_bufsize, wal_grp_cmt_wait, lc_messages, lc_ctype, cache_manager, shutdown, online, shutdown_delay, reserved, overwrite,
sec_attach, disable_wal, connect_timeout, dummy_packet_interval, gbak_attach, sql_role_name, set_page_buffers, working_directory, sql_dialect,
set_db_readonly, set_db_sql_dialect, gfix_attach, gstat_attach, gbak_ods_version, gbak_ods_minor_version, set_group_commit, gbak_validate,
no_db_triggers, trusted_auth, process_name, instance_name, old_overwrite, utf8_filename, sys_encrypt_password, wirecompression

FredS wrote: ↑Wed 23 Jan 2019 23:20 Thanks, this works in the latest release but I still can't see it in the Help file.

We will add the necessary information in UniDAC (IBDAC) help in one of the next UniDAC (IBDAC) builds.

FredS wrote: ↑Fri 28 Dec 2018 22:24 Adding it in code gives me this:

Code: Select all

"WireCompression" is not a valid option name for InterBase UniProvider.

What is the correct way of using 'WireCompression'? I looked for it in the help file but no luck, yet 'History.html' shows it added in 7.1.3.

I get the very same error message in UniDAC 8.3.2.

frickler wrote: ↑Thu 07 Jan 2021 14:21 I get the very same error message in UniDAC 8.3.2.

Works for me:

FredS wrote: ↑Thu 07 Jan 2021 16:57

frickler wrote: ↑Thu 07 Jan 2021 14:21 I get the very same error message in UniDAC 8.3.2.

Works for me:

Code: Select all

Con.SpecificOptions.Values['InterBase.Params'] := 'WireCompression=true';

I thought this was the workaround until the parameter "WireCompression" is natively supported (with the next UniDAC build).

Hello,
Yes, we've added the WireCompression parameter - it will be included in the next release of UniDAC. As a workaround, you can use wbr, Oleg
Devart Team

it will be included in the next release of UniDAC

Still get this in 9.0.1 (19-Nov-2021)

By looking into the sources one can clearly see, that it's only working if you use IBDAC with UniDAC Express ("Lite"). If you don't, then you have to use the "WireCompression=true" method instead.