search

fsprojects / Rezoom.SQL

Statically typechecks a common SQL dialect and translates it to various RDBMS backends
MIT License
669 stars 25 forks source link

How to determine corresponding sql file during error on migration #17

Closed rkosafo closed 6 years ago

rkosafo commented 7 years ago

Is there a way to indicate or determine the sql file responsible for an error during migration?

When there are migration errors (from using the vendor statement a lot), the exception shown is the correct sql error but when multiple sql files were added running the application, it can be a bit difficult to identify which file generated the error.

Example error 2017-08-22 01_32_59-notificationsform

rspeele commented 7 years ago

Good point, these should probably be wrapped in an outer exception containing the filename.

rkosafo commented 7 years ago

@rspeele What is the final decision on this? Is it to write the outer exception as indicated above or have you decided on some other approach?

rspeele commented 7 years ago

Definitely outer exception as above and it's honestly a tiny change, I have just been completely unmotivated in the past couple months. Sorry!

(edit: I have written a commit to help with this, hoping to fix a few of the other quick issues before putting up a new NuGet package)