title: Oracle's Beta EF Provider - Why won't it let me map a Decimal to a "number" field
body: <p>So... I downloaded and installed Oracle's Beta version of their EF provider... Why? Because nothing else seemed to work very well (i tried the one on CodePlex as well as the one on MSDN), and my company is not going to pay for a commercially available one (like the one from devart).</p>
  
  <p>So, it worked great. I was able to see the oracle database, select the particular schema I was interested in, pull in the table definitions. Great!</p>
  
  <p>Now I get an error. It seems the default behavior of the provider is to map number(1,0) fields to boolean types in .NET. Not good, but, I should be able to change this, right? The error I got was something along the lines of "the types don't match". So I change the definition of that field to a Decimal(1,0). </p>
  
  <p>Now, the new error I am getting is that decimal(1,0) is not compatible with number(1,0). And I am stuck. I cannot make a change to the mapping to anything that works.</p>
  
  <p>I don't like using Oracle to begin with because they seem to be a couple of years behind supporting anything .NET related. Now, I am ready to give up on them altogether.</p>
  
  <p>So, my question is this... I this <em>any way</em> besides the devart components that I can get Oracle working with EF? It would make my life simpler if I can. If not, then I get to hand-code all of this goodness... or tell the partner to switch over to SQL server since it's just as good (for what they are doing with it...)</p>