Hello:
> This question is about the handling of parameter overflow in the
> Firebird.NET Provider. If you do something along these lines:
>
> c:=FbCommand.Create('select * from zip where zip_code=?',
> FbConnection1);
> c.Parameters.Add('', FbDbType.VarChar).Value:='123456'; <<-
At 03:29 PM 2/04/2007, you wrote:
>Max no. of columns in Firebird is 255
Not true.
>, and max row size is 64K,
Yes
>so no. of columns will depend upon the column type you are using
Yes.
There is also a limit of 64 K bytes for the length of a single SQL statement.
>On 4/2/07, Gary Saunders
Max no. of columns in Firebird is 255, and max row size is 64K, so no. of
columns will depend upon the column type you are using.
Manish
On 4/2/07, Gary Saunders <[EMAIL PROTECTED]> wrote:
Is there a limit to the number of columns I can access or create through
the
.net provider. I have a co
Is there a limit to the number of columns I can access or create through the
.net provider. I have a command that attempts to create over 250 columns in
a new table. I can only get 20 some columns if the column type is varchar
and 256 if they are integer.
--
Kevin Donn wrote:
> and zip_code is defined to be varchar(5), you'll receive an
> isc_arith_except error. In the Delphi TDataSet world, if you write a
> parameterized query like this, and then supply a value that is too long,
> it will in general be shortened to fit and no error returned or
>
