-
Notifications
You must be signed in to change notification settings - Fork 18
Table name and Schema in Configuration Settings should accept any form of case #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sorry, it does not go outside |
I have managed to get it working now, and it does work out of the box, it just doesn't bubble any errors up if theres an issue when interacting via the session. I had set up the configuration to use camel casing in the schema and table names, but it seems that when the tables are created they are created in lowercase, so they then can't be found when the code runs. I only found this when I injected the IDistributedCache in the PageModel, as it does throw an exception there. Changed the schema and table name to all lowercase and it works a charm. Thanks |
Might be worth updating the documentation to state that lowercase names are required? |
Actually yes, I think I can update to use both forms, I will look into this |
I have tried to set this up and use HttpContext.Session (like you can with Redis) but nothing is stored/retrieved, any ideas? Is there some extra configuration required to enable this or is it not supported?
The text was updated successfully, but these errors were encountered: