Currently we use Sql Anywhere with EntityFramework and we simply map stored procedures onto the context. We have an issue with nullable fields in a table. When we create a complex type ( as a return data from a stored procedure ), all fields which are nullable in the database are marked as not null in the complex type and thus fail when we actually try to call that sp.

We have to manually set all fields to nullable on the complex type. If we need to update a stored procedure then the complex type gets all its properties back to non nullable and starts failing again so we have to repeat the process.

Any chance this annoying bug can be solved ?

asked 15 Oct '13, 05:36

Sparkstone's gravatar image

accept rate: 0%

Please provide your SQLA Version for reference

(15 Oct '13, 06:41) Martin
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 15 Oct '13, 05:36

question was seen: 2,264 times

last updated: 15 Oct '13, 06:41