You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously OrmLite only supported serializing Complex Types with a [single Complex Type Serializer](https://docs.servicestack.net/ormlite/complex-type-serializers)
198
-
but with new configuration model now uses a more configurable `JsonComplexTypeSerializer` where you can change the default
199
+
but the new configuration model now uses a more configurable `JsonComplexTypeSerializer` where you can change the default
199
200
JSON Serializer OrmLite should use for serializing Complex Types as well as fine-grain control over which types should
200
201
be serialized with which serializer by using the `.ConfigureJson()` extension method for each provider.
201
202
@@ -331,10 +332,9 @@ The new `TableRef` struct allows for unified APIs that encapsulates different wa
331
332
- Quoted Name (use verbatim) `TableRef.Literal("\"MyTable\"")`
332
333
- Implicitly casts to a string as `new TableRef("MySchema")`.
333
334
334
-
OrmLite handles differences between different RDBMS Providers via its `IOrmLiteDialectProvider` interface which is
335
-
responsible for handling all differences between different RDBMS Providers. OrmLite used to maintain multiple overloads
336
-
for handling some of these differences in referencing a table but they've now all been consolidated into use a single
337
-
`TableRef` parameter:
335
+
OrmLite handles differences between different RDBMS Providers via its `IOrmLiteDialectProvider` interface.
336
+
Previously OrmLite used to maintain multiple overloads for handling some of these differences in referencing a
337
+
table but they've now all been consolidated into use a single `TableRef` parameter:
0 commit comments