Closed Chralex closed 6 years ago
Hi!
Thanks for the feedback and the suggested changes. I was about to build the 1.2.0 release of the package but I have been a bit delayed since the windows 10 1803 update killed my Dev laptop.
Sorry to hear about your laptop. Last time a windows update damaged one of my machines was back in the Windows Vista days, where upgrading the service pack caused my sound card to stop working. That was pretty annoying.
Hi there, I ran into some issues when using this since I'm using some not ideal column names for a table that is used to hold integration data. To be more specific I have a column named "Key", which is a SQL keyword. As said earlier I only chose that name because the provider uses the same name for their column in another database.
This basically prevents the SQL-interpreter from reading the column name as a keyword.
For posterity here is the exception that I got:
And that is because my table-class looks like this:
I realize that it is possible that you intended that the developer should solve this by providing their own column mapping via an attribute?
p.s. I see that you fixed some garbage collection issues, please make a release package for them. Thank you.