todo:pdounicode
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | todo:pdounicode [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | Here are some notes from the meeting yesterday. | ||
+ | |||
+ | The plan is to avoid conversions if we can. | ||
+ | |||
+ | We'll introduce a PDO:: | ||
+ | |||
+ | * PDO:: | ||
+ | * PDO:: | ||
+ | * PDO:: | ||
+ | * PDO:: | ||
+ | |||
+ | It would also be nice to be able to pass in an IANA charset encoding name and have that work, but we needn' | ||
+ | |||
+ | The charset attribute will specifiy the default disposition for data going in and coming out from the database. | ||
+ | |||
+ | The driver will take this value and attempt to set the server connection to use that character set, so that the data that is returned matches the expectation and eliminates the need to perform an explicit conversion. | ||
+ | |||
+ | When a dataset is fetched and the columns described, each column will have some encoding information; | ||
+ | |||
+ | The doer and preparer driver methods need to be expanded to accept a parameter that specifies whether the input is 8bit (binary or the PDO:: | ||
+ | |||
+ | When passing parameters into the driver, it will be responsible for handling any conversions that might be required to pass that data to the server. | ||
+ | |||
+ | Let's think on this for a couple of days before we specify exactly where these bits fit in the structures and so on. | ||
+ | |||
+ | --Wez. | ||
todo/pdounicode.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1