Categorías: Todo - culture

por Samy Sarem hace 2 años

119

2022-01-31 Oracle

The document outlines various tasks and considerations related to Oracle database management and integration within a software environment. It highlights the need for proper handling of date and datetime formats in prompts and filters, and emphasizes the importance of using the correct data source converters that account for all properties, including pooling and schemas.

2022-01-31 Oracle

2022-01-31 Oracle

Oracle.ManagedDataAccess.Client

See DbProviderFactoriesRegistrator for .Netframework
Wrong name ?? Should be Oracle.ManagedDataAccess
Name is correct as per oracle documentation

Things to check

Prompts / selection page data format
Using in filters

sqlGen

Mostly dates and datetimes
Culture
Test Oracle ou SQL french
DBProvider

System_Data_SqlCient_Provider

RecordReaderOfArrayOfStrings

Check commit fd1b2b84 for other changes

For the culture, supposed to be handled already

RequestDAL

NecDefaultCulture

ORACLE_DataSourceConverter
Takes into account all properties possible

extra connection properties

schemas

pooling

Todo

Adding management of dbtype
Is cas necessary for all fields ?

Check how nectari currently handles casts

Just calculations maybe ?

What if a view has a calculation (decimal issue)

sqlgen
we use mostly process, not sqlcolumnsmedata

should we switch it to use as much as possible from sqlColumnsMetadata instead ?

BIMetadataHandler timeout
What to use for regular queries ?

Do we have a setting in Env & Datasources ?

What to use ?
DBExpression joins add a Concat type
Create new concat | reuse existing one ?

Add unit tests in dbExpression tests unit tests

Fix test ?

Technically it makes sense, just not for joins

Check dbExpressions from Microsoft

Is this our implementation or Microsofts ?

SyntaxDictionary

Check dbExpression tests for Oracle and other providers

Test passes but doesn't make sense

Check if Datasync has usage for concat

VisitConcatExpression is only overriden for Oracle and base QueryTranslator

Was there a specific reason why we needed || in datasync ?

Investigate in code / test datasync with oracle with fix

Part of OG implementation

Could it be related to Oracle version

Concat is only used in joins at the time being

Not meant for joins
Meant for use in values (select, join conditions, filters ...)
Adds "||" in between arguments
Alias name too long for fields
Done but what about tables ?

Tables have same problem

Is this case likely to happen?

Make test worksheet
Use Datasync Driver
Reload config on the fly
Oracle versionning

Ensure it works with packages

dotPeek

Doc on how to configure provider

publictoken guid and version to add to nectariinstaller

Find proper place and syntax

New oracle connection pour test la dll
ManagedDataAccess
BIMetaDataHanlder
In that case the caching must be by user or not include the sanitization
What gets cached may be sanitized ?

SmartCacheService does not sainitize

Need to confirm

Issues

DBProviders
Does not have manageddataaccess
BaseBIQueryResolver
schemas count is empty
QueryResolverFactory
For now, added a copy

remove copy ?

Is ManagedDataAccess the right one ?
Cannot find type BIQueryResolver.Oracle_ManagedDataAccess_Client_QueryResolver, BIQueryResolver