* refactor: remove oracle docker tests and update DEVELOPER.md
Since oracle runs at thin mode now. Now extra docker tests are needed
* chore: increase oracle version to 21c
* feat: add json column types to oracle
* fix: try to resolve pipeline issue to increase oracle waiting time
* fix: try remove networks from oracle to fix pipeline
* fix: add container name
* fix: add missing oracledb driver in package-lock.json
* fix: corrected tests
* fix: remove tests, since only work with old oracle db
* fix: correct tests
* fix: remove deprecated types
* fix: add missing grant for materialized views
* fix: oracle-isolation.ts test
* fix: issue-3363.ts test
* fix: schema in tests
* feat: implement or operator
This new feature enables typeorm to allow use multiple operators joining with or
Closes: #10054
* feat: implement or operator
Completed code formating using command.
Closes: #10054
* feat: implement or operator
Completed the documentation update.
Closes: #10054
* feat: implement or operator
Renamed Or operator file name.
Closes: #10054
* feat: implement or operator
Renamed Or operator file name.
Closes: #10054
* feat: implement or operator
Renamed Or operator file name.
Closes: #10054
* feat: implement or operator
Renamed Or operator.
Closes: #10054
* feat: add support for mssql@10
Add mssql@10 to peerDependency, alongside mssql@9.
Update tests to use latest version of mssql and Node v16.
Closes: #10340
* fixed failing test
---------
Co-authored-by: Alex Messer <dmzt08@gmail.com>
* fix: extend spatial column types for postgres driver
Extend spatial column type with range types for postgres. This fixes a bug when using spatial indices.
Closes: #10567
* format
* remove only from test, ready for pr
* changed a way how we determine index type
---------
Co-authored-by: Dmitry Zotov <dmzt08@gmail.com>
* Add a replication test suite
* Allow overriding the default destination for read queries when using replication
For many applications that want to use read slaves, data consistency isn't super important, and so all reads can be sent by default to a read slave. For some applications though, it's only select queries that can be sent to read slaves as end-users of the application expect data consistency almost everywhere. This new setting lets apps like those change the default such that query builders need to opt *in* to sending to a read slave, instead of opt out.
* test: fix migration-generate test suite
WIP
Closes: #10360
* fixed mssql test hang;
added option to disable process exit;
---------
Co-authored-by: Alex Messer <dmzt08@gmail.com>
Disabling the raft log is going to be disallowed in CockroachDB. Also,
this setting wasn't having any effect, since the tests use an in-memory
cluster.
* fix: ensure comparing EntityMapIds in `buildForSubjectRelation`
I have found the issue (for me at least). In the method `buildForSubjectRelation` of `ManyToManySubjectBuilder`, in order to know if it is needed to insert the relation rows `databaseRelatedEntityIds` is compared with `relatedEntityRelationIdMap` (line 154). The problem is that `databaseRelatedEntityIds` is not always an "EntityIdMap". If one is overloading the entity in the `afterLoad` event of an EventSubscriber for example the line 102 :
`const databaseRelatedEntityValue = relation.getEntityValue(subject.databaseEntity);` will return an "enhanced" object with additional properties. To fix this, in this commit, we ensure that `databaseRelatedEntityIds` is containing an "EntityIdMap".
Closes#5704
* refactor: describe.only -> describe
removes describe.only.
* style: npm run format
format code.
* Update issue-5704.ts
refactor: typo on post title
---------
Co-authored-by: blemoine <services+bitbucket@blemoine.pro>
* fix: resolve issue building eager relation alias for nested relations
Fix alias error for nested relations. When loading eager relations from
nested levels only the first level was handled through the alias builder
Closes: #9944
* fix: update test: issue-9944 to include postgres
Add postgress as enabled driver for test "issue-9944"
* fix: resolve issue building eager relations withput parsing for "." to get relations
Fix alias error for nested relations by usinf relation.propertyName instead of relation.propertyPath
By using property path, we would have to parse for "." to get the nested relations, but that could
bring issued with column names that had dots within the name.
This adds a new property `disableAsciiToUnicodeParamConversion` to `SqlServerConnectionOptions` to
control whether the `MssqlParameter` types char, varchar, and text are converted to their unicode
equivalents, nchar, nvarchar, and ntext. This defaults to false, maintaining the current behavior.
Closes: #10131
