![]() ![]() MySQL distributions now include lz4_decompress and zlib_decompress utilities that can be used to decompress mysqlpump output that was compressed using the -compress-output=LZ4 and -compress-output=ZLIB options. Disabling innodb_support_xa is no longer permitted as it makes replication unsafe and prevents performance gains associated with binary log group commit. InnoDB support for two-phase commit in XA transactions is always enabled as of MySQL 5.7.10. InnoDB: The innodb_support_xa system variable, which enables support for two-phase commit in XA transactions, is deprecated. InnoDB: Enabling the new innodb_background_drop_list_empty debug configuration option helps avoid test case failures by delaying table creation until the background drop list is empty. For more information, see Secure Connection Protocols and Ciphers. By default, MySQL attempts to use the highest TLS protocol version available, depending on which SSL library was used to compile the server and client, which key size is used, and whether the server or client are restricted from using some protocols by means of tls_version/-tls-version. The mysql_options() C API function has a new MYSQL_OPT_TLS_VERSION option that enables specifying from within the client library the TLS protocols permitted by a client program. On the client side, the -tls-version option enables specifying the TLS protocols permitted per client invocation. The tls_version system variable enables specifying at startup the TLS protocols permitted by the server. To enable TLSv1.2 support if you build from source, you must set the WITH_SSL CMake option to use OpenSSL. ![]() Because TLSv1.2 requires OpenSSL, support for this protocol is available in binary distributions only for MySQL Commercial Server, and not for MySQL Community Server (which is compiled using yaSSL). TLS support is now extended to enable a higher level of encrypted connection security: when compiled using OpenSSL 1.0.1 or higher, MySQL supports the TLSv1, TLSv1.1, and TLSv1.2 protocols when compiled using the bundled version of yaSSL, MySQL supports the TLSv1 and TLSv1.1 protocols. I'm personally using the latest ZEOS 7.- Previously, MySQL supported only the TLSv1 protocol for encrypting secure connections. If the application is 32bit then the dll must be 32bit also, same for 64bit. It is only that your application must load the proper dll for itself. The MySQL database itself does not matter whether 32 or 64bit, both the 32bit/64bit DLL can access them. Whichever your compiled executable is (Win32 or Win64), you need to load the proper 32 or 64bit LibMySQL.dll for it. "Unit output directory" to "units\$(TargetCPU)-$(TargetOS)" so I can see what files are what. I also put the "Target file name" to "something-$(TargetOS)" and the In the Lazarus "Project -> Project Options -> Code Generation" use the "Target OS" and "Target CPU Family" to make sure you either have "Win64/x86_64" or "Win32/i386" pair (of course you need the proper fpc units for both pairs). I am using the 32bit Lazarus and have cross-compiling to 64bit if I need 64bit applications.īy having 64 bit Lazarus does not guarantee that your compiled app is 64bit. I am able to create both 32bit and 64 bit Apps to use MySQL on my 64bit Windows machine (to connect to MySQL via tcp/ip locally or to remote servers). Am I better off Installing 32 Bit Lazarus, if so, what implications does that have for Windows 7 compatibilty? Where can I get a version of libmysql.dll that is guaranteed 64 Bits?Ģ. "Cannot load default MySQL Library ("libmysql.dll" or "libmysql.dll"). I have the 64 bit version of lazarus installed and I have tried both the 32 bit and (I think) the 64 bit version of libmysql.dll to no avail. I have copied the source for these to my new machine after downloading and installing Lazarus and BOOM!! I have the libmysql.dll in the application directory,and everything is hunky-dory. I have numerous Applications that talk to my MySQL Databases on my server, they all run fine on my old XP(SP3) machine. I have a Dell N5040, Windows 7(64 Bit), Lazarus 1.04, FPC Version2.6.0. I know this has been covered elsewhere(I think I've read most of the threads!),but I can't get this working. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |