Open lloydchriswilson opened 5 months ago
Can you send a PR for this if you have fixed it as you mentioned in another issue?
Actually I did not fix the DuckDB code, I just modified my code to conform to DDB expectations.
From: Giorgi Dalakishvili @.> Sent: Monday, June 24, 2024 3:43:39 PM To: Giorgi/DuckDB.NET @.> Cc: Chris Wilson @.>; Author @.> Subject: Re: [Giorgi/DuckDB.NET] Parameter names (Issue #203)
Can you send a PR for this if you have fixed it as you mentioned in another issue?
— Reply to this email directly, view it on GitHubhttps://github.com/Giorgi/DuckDB.NET/issues/203#issuecomment-2187460731, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFIQZM3SRWRAYX4CBQLQF6DZJCHIXAVCNFSM6AAAAABJ2HRF46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBXGQ3DANZTGE. You are receiving this because you authored the thread.Message ID: @.***>
In DuckDB when you set a query parameter name, all other providers I use (SQLite, SQL Server, Oracle, MySQL, etc.) are forgiving if you include the SQL prefix when defining the parameters (e.g., you can pass $PARM1 as the parameter name) and it works OK, however DuckDB requires that the name exclude the prefix (e.g., PARM1).