Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Modifying Attached Table Twice Returns Error #1133
Details for the issue
OK, another "but this is never going to happen in real life!!" case, but thought I'd mention it....
I guess you can't prevent it, but didn't know if the error could be 'sugared' somewhat for the user, so they had an inkling that they couldn't do what they're trying to do.
* For the avoidance of doubt, this was my schema.
a, b, and c are all the same attached database - just different names. The 'main' database is a different database (so I'm not attaching itself, if that makes sense...)
Useful extra information
I'm opening this issue because:
I'm using DB4S on:
I'm using DB4S version:
I have also:
added a commit
Oct 5, 2017
Yeah, I can't come up with any reasonable way to make this work either. So I have just added some code now which forbids attaching the same database twice. It's definitely better to just prevent the entire issue this way. Are you ok to double check, @chrisjlocke? Sorry for all the testing I ask for today
added a commit
Oct 6, 2017
Where did you find this picture of me?!
I've just pushed a commit which (hopefully) makes the path and file name comparison case-independent on Windows. Maybe this already fixes your issue, so it's worth testing it again tomorrow. And if it doesn't fix your issue the commit is still fixing some bug at least