jkort

Clearly this exceeds my capabilities. Goal was to get to a 64bit version of tds_fdw. Building FreeTDS 0.95.87 with this: > nmake /A /I -fNmakefile -nologo apps PLATFORM=x64 CONFIGURATION=release >...

Thanks Geoff, The only library created by the nmakefile is db-lib.LIB, I get no .DLL I imagine I'm doing something very basic incorrectly.

Realized I could use Cmake instead of Nmake, so started over with FreeTDS. Got FreeTDS to build, then after many iterations of adding .LIB dependencies under VS, got a tds_fdw.DLL...

I may have solved my own problem using ALTER FUNCTION ... RENAME TO ...

The SQL in \share\extension\ with the control file was changed to this to accommodate the prefixed function names I see in the tds_fdw.DLL: CREATE FUNCTION pg_finfo_tds_fdw_handler() RETURNS fdw_handler AS 'MODULE_PATHNAME'...

Found a similar posting about "pg_finfo_" prefixing, with no clear direction on what preprocessor definitions I could use in my Visual Studio project to fix the function creations: http://stackoverflow.com/questions/13776232/why-does-c-name-link-symbol-of-the-specific-function-should-be-prepended-with

I realized I had not followed Craig Ringer's requirement to have a PGDLLEXPORT prototype, so I added these first two lines to tds_fdw.c: PGDLLEXPORT Datum tds_fdw_handler(PG_FUNCTION_ARGS); PGDLLEXPORT Datum tds_fdw_validator(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(tds_fdw_handler);...

Thanks Geoff! I was ready to give up and stop bothering you. Took me a bit as a newbie to find the log; here's what it shows around that SELECT...

Thanks Geoff! I'm sure there are numerous places I could have gone wrong. If I can figure out how to run this under a debugger I will. Any time you...

https://github.com/vega/voyager