My reply to Maxime was regarding his use of the "Oracle.DataAccess" provider. I don't think the SQLite provider is going to be a problem.
I took another look at Maxime's debug information when using Varchar2 types and the Oracle provider: > - Not good (when Size set to 0) : > m_maxSize 0 int > m_modified true bool > m_precision 0 byte > > - Good (when Size set never set) : > m_maxSize -1 int > m_modified false bool > m_precision 100 byte and thought of another possible solution using parameterMaps. He should be able to use a parameterMap to specfy the size, precision, and scale of the Varchar2 parameters that are causing him trouble: <parameterMap id="insert-params"> <parameter property="NomUsager" dbType="Varchar2" size="-1" precision="100" /> <parameter property="Nom" dbType="Varchar2" size="-1" precision="100" /> <parameter property="Prenom" dbType="Varchar2" size="-1" precision="100" /> </parameterMap> Yes, I know Size isn't allowed to be less than zero (Line 193 of DefaultPreparedCommand.cs). I would classify my above example as a "hack" that should be ignored unless Maxime's still isn't able to fix his problems with his version of the Oracle provider... --- Gilles Bayon <[EMAIL PROTECTED]> wrote: > The size property is set for ALL DbTypes and we will not make > exception for one DbType and not for an other. > We try to make generic code and not specific code, if SQLite.NET > provider is a special provider, ask SQLite.NET team to modify their > code to follow .NET guidelance. > > We have introduced the generic size/precision/scale properties on > provider to try to fix odp.net and by the way some SQLite.NET issue > but we will not go on specific code. > > -Gilles >
