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
Copy file name to clipboardExpand all lines: AppenderMap-Usage.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,19 @@
1
-
# ClassMap-based Type-Safe Appender
1
+
# AppenderMap-based Type-Safe Appender
2
2
3
-
This implementation provides a type-safe way to append data to DuckDB tables using ClassMap-based mappings with automatic type validation.
3
+
This implementation provides a type-safe way to append data to DuckDB tables using AppenderMap-based mappings with automatic type validation.
4
4
5
5
## Problem Solved
6
6
7
-
The original issue was that users could accidentally append values with mismatched types (e.g., `decimal` to `REAL` column), causing silent data corruption. The ClassMap approach validates types against actual column types from the database.
7
+
The original issue was that users could accidentally append values with mismatched types (e.g., `decimal` to `REAL` column), causing silent data corruption. The AppenderMap approach validates types against actual column types from the database.
8
8
9
9
## How It Works
10
10
11
-
### 1. Define a ClassMap
11
+
### 1. Define an AppenderMap
12
12
13
-
Create a ClassMap that defines property mappings in column order:
13
+
Create an AppenderMap that defines property mappings in column order:
14
14
15
15
```csharp
16
-
publicclassPersonMap : DuckDBClassMap<Person>
16
+
publicclassPersonMap : DuckDBAppenderMap<Person>
17
17
{
18
18
publicPersonMap()
19
19
{
@@ -61,7 +61,7 @@ The mapped appender retrieves actual column types from the database and validate
0 commit comments