mirrors/pgloader
1
0
Fork 0
mirror of https://github.com/dimitri/pgloader.git synced 2026-05-05 10:56:10 +02:00
Code Issues Projects Releases Wiki Activity

Add some docs about FreeTDS and encoding.

Browse Source 
It turns out that it's possible and not too complex, when using the
FreeTDS driver, to enforce the client encoding for MS SQL to be utf-8.
Document how to tweak ~/.freetds.conf to that end.
This commit is contained in:
Dimitri Fontaine 2017-01-27 22:16:59 +01:00
parent 1d025bcd5a
commit ed217b7b28
2 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
pgloader.1
View File

@ -2805,6 +2805,21 @@ The matching is done in pgloader itself, with a Common Lisp regular expression l
.
.IP "" 0
.
.SS "Driver setup and encoding"
pgloader is using the \fBFreeTDS\fR driver, and internally expects the data to be sent in utf\-8\. To achieve that, you can configure the FreeTDS driver with those defaults, in the file \fB~/\.freetds\.conf\fR:
.
.IP "" 4
.
.nf
[global]
tds version = 7\.4
client charset = UTF\-8
.
.fi
.
.IP "" 0
.
.SS "DEFAULT MS SQL CASTING RULES"
When migrating from MS SQL the following Casting Rules are provided:
.

10
pgloader.1.md
View File

@ -2303,6 +2303,16 @@ The `mssql` command accepts the following clauses and options:
expression lib, so doesn't depend on the *LIKE* implementation of MS
SQL, nor on the lack of support for regular expressions in the engine.
### Driver setup and encoding
pgloader is using the `FreeTDS` driver, and internally expects the data to
be sent in utf-8. To achieve that, you can configure the FreeTDS driver with
those defaults, in the file `~/.freetds.conf`:
[global]
tds version = 7.4
client charset = UTF-8
### DEFAULT MS SQL CASTING RULES
When migrating from MS SQL the following Casting Rules are provided: