Skip to content
This repository was archived by the owner on Dec 24, 2022. It is now read-only.

Conversation

@pysco68
Copy link

@pysco68 pysco68 commented Jul 25, 2013

The issue can be fixed by setting the constructor parameter "parseViaFramework" of SQLiteConnection to true.

Only few documentation is available about that change that was apparently introduced with bugfix http://sqlite.1065341.n5.nabble.com/3-7-7-URI-filenames-and-UNC-paths-td6893.html

N.B.: I don't know wether or not the Mono version is affected.

…y to open databases when the path is for example a UNC path.

The issue can be fixed by setting the constructor parameter "parseViaFramework" of SQLiteConnection to true.
@mythz
Copy link
Member

mythz commented Jul 25, 2013

Can you provide the failing test that this fixes please.

@pysco68
Copy link
Author

pysco68 commented Jul 26, 2013

I'm taking a look at it, but I'm afraid it'll be hard to test because the test would certainly rely on environment conditions, as I discovered the bug trying to save the database on a path like \server\folder\xxxx (a windows share, not being mounted as network drive)

@pysco68
Copy link
Author

pysco68 commented Jul 26, 2013

I didn't find any practical way of simulating a UNC path. I can't think of a way of solving this. Sorry.

@mythz
Copy link
Member

mythz commented Jul 26, 2013

ok but how do we know this change is safe and doesn't break anything?

@KevinHoward
Copy link
Contributor

http://stackoverflow.com/questions/16768415/system-data-sqlite-parseviaframework

It appears that this new "parseViaFramework" parameter for the SQLiteConnection constructor was created to address a completely different issue, so I can see @mythz concerns.

Do both of you feel that building unit tests and code changes around the issue it did solve would suffice to addressing the changes for the UNC paths?

@mythz
Copy link
Member

mythz commented Jul 26, 2013

Right, I don't like changing default behavior without any assurances. In the meantime lets add a static field that's defaults to false on SqliteOrmLiteDialectProviderBase and use that in the constructor.

@pysco68
Copy link
Author

pysco68 commented Jul 26, 2013

Sure that would help, and I fully understand the point of wanting some insurance, but I really don't know how one should build a test case for that one (I mean that I'm not aware about any shared folder that is always available, plus that test would be windows only).

I'd be happy to help further if s someone gives me a hint.

Demis Bellot notifications@github.com schrieb:

I don't like changing default behavior without any assurances. In the meantime lets add a static field that's defaults to false on SqliteOrmLiteDialectProviderBase.


Reply to this email directly or view it on GitHub:
#290 (comment)

@mythz
Copy link
Member

mythz commented Jul 26, 2013

Ok this should do it: 6773868

You need to set SqliteOrmLiteDialectProviderBase.ParseViaFramework = true before you connect.

@mythz mythz closed this Jul 26, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants