Support all MySql.Data Connection String options #105
Comments
|
AFAIK, |
|
What is the possibility for getting "Treat Tiny As Boolean" support?
Is the current handling set to true? I'm having an issue with Pomelo.EntityFrameworkCore.MySql when tinyint(1) is used.
Edit: I located the code to change and I found what the official connector does. |
|
The current default for |
|
(FWIW, converting |
|
@bgrainger Thanks, that's the workaround I'm currently using. Also |
|
The link in the first post is dead, this is the current one |
|
Are you planning to support the TableCaching option? I'm surprised this isn't supported, particularly since this library emphasizes performance. In many scenarios, table caching could make reading hundreds of times faster. |
|
Have you previously used the Table Caching option with Connector/NET? The documentation seems very sparse and the only scenario I'd see it being compatible with is when UPDATE: I just looked at the source code for MySqlDataReader class and that is indeed the limitation. If that's the usage then you might just as well implement the caching yourself in your own application. |
|
OK, I understand. |
|
The data may not be changed frequently, but, it does change. In my apps, I would rather have accurate data. So, I would be inclined to stay away from something like that. Particularly, for something like user or role information. I guess it depends on what the cache timeout is. |
|
|
@mguinness Thanks for the analysis; I had not researched the @bkonia Caching seems like an application-level concern that should be handled at a higher level, not a feature of an ADO.NET library. (I'm not aware of an analogous option in any other ADO.NET library.) Also, since this is effectively a no-op for almost all Connector/NET queries (I suspect very few clients actually use |
|
This is typically referred to as 2nd level cache. Some ORMs, e.g. NHibernate, implement it, EF6/Core don't, though there are extension packages. Somewhat off topic: I personally prefer to steer clear and do things like user profile caching on application level. Some modern web API apps using JWT auth may not need it at all - depends on whether you need any sensitive user data on your every API request or not. If you do, cache in the app, if you don't just add to your JWT. That's actually one of the main "selling points" of JWTs compared to traditional session IDs - to be able to avoid hitting the DB on every request. |
|
Every option is either implemented, deliberately not implemented, or (just one: SSH settings) isn't implemented yet but has a documented workaround. |
|
Any plans for supporting |
What's the use case where you'd want to use it? |
|
As I understand, it's required for password-less Kerberos authentication. |
|
Right, but MySqlConnector doesn't support |
From Connection String Options Reference:
AllowBatchtrueby default, and there doesn't seem to be much point in supportingfalseAllowLoadLocalInfileAllowLoadLocalInfileInPathAllowUserVariablesAllowZeroDateTimeAutoEnlistCacheServerProperties@@max_allowed_packet, @@character_set_clientetc. when connectingCertificateFileCertificatePasswordCertificateStoreLocationCertificateThumbprintCharacterSetutf8mb4in this connector; unclear if being able to use a different encoding on the wire has clear benefitsCheckParameterstrueby default;check parameters=falseseems to be recommended only as a work around for Connector/NET bugs or MySQL permission problemsCommandInterceptorsConnectionLifeTimeConnectionResetConnectionTimeoutConnect_AttrsConvertZeroDateTimeDatabaseInitialCatalogDefaultAuthenticationPluginDefaultCommandTimeoutDefaultTableCacheAgeTableCacheDnsSrvEnableSessionExpireCallbackfalse; manipulatesmy_aspnet_sessionstableEncryptExceptionInterceptorsFunctionsReturnStringfalse; unaware of any clients that need thisHostIgnorePrepareincludesecurityassertsInteractiveSessionIntegratedSecurityKeepaliveLoggingMinimumPoolSizeOldGuidsOldSyntaxOpenidIdentityTokenPasswordPassword1,Password2,Password3PersistSecurityInfoPipeNamePoolingMaximumPoolsizePortProcedureCacheSizeConnectionProtocolsocketandunixare supported (and auto-detected)ReplicationRespectBinaryFlagstrueby defaultSharedMemoryNameSshHostName,SshPort,SshUserName,SshPassword,SshKeyFile,SshPassPhraseSslCaSslCertSslKeySslModeSql Server ModeTableCacheCommandType.TableDirect; seems low-value; caching is better handled at the application layertlsversionTreatBlobsAsUTF8utf8mb4; also includesBlobAsUTF8ExcludePattern,BlobAsUTF8IncludePatternTreatTinyAsBooleanUseAffectedRowsUseProcedureBodiesUserIDUser nameUseCompressionUseUsageAdvisorUsePerformanceMonitorThe text was updated successfully, but these errors were encountered: