Comments
Sort by recent activity
Hello Luke. Thanks for the prompt reply (no pun intended)! I must admit I've used SQL Prompt for a long while and this is the first I've seen it. I am able to reproduce the issue on other machines, but I had to at least see if it was just occurring on my regular workstation. I am hoping that I am the only one seeing the issue as I couldn't find it in the forums.
As to your question of its importance to me, I'd like to see an update for a fix if the developers can discover how locale detection might fail if that's the case or an update for an option to counteract the default behavior. It might be a real problem for those relying on exacting precision for their date/time columns, especially if their data sets are large and they don't catch it early.
In my case, the issue doesn't affect me quite as much. I certainly demand precision in my data sets when I can control the outcome, but I usually change the static suggestion for the date/time output of the template anyway. I always change it to GETDATE() as I may take quite some time to revise the statement, especially when integrating the INSERT statement into a larger procedure. I would actually love to see an option to specify a function such as GETDATE() be written to the statement, rather than writing the actual output of GETDATE() directly. I am making an assumption that the code base is doing just that. That would save me the same ton of time that SQL Prompt already brings to my table!
Thanks for your solicitation. / comments
Hello Luke. Thanks for the prompt reply (no pun intended)! I must admit I've used SQL Prompt for a long while and this is the first I've seen it. I am able to reproduce the issue on other machin...