Probably you inserted a too long string in a small field.

Example: you get this error if you want to insert "ABCDEFG" in a Varchar(5) 
sized field. (this string need 7 chars)




________________________________
 From: Allstars <d...@stepstoliteracy.com>
To: firebird-support@yahoogroups.com 
Sent: Wednesday, May 15, 2013 10:35 PM
Subject: [firebird-support] Re: Unable to INSERT INTO TABLE
 


  
Ok sorry, now I am getting a different error. When I do the insert,

I'm getting a 

Error: arithmetic exception, numeric overflow, or string truncation
string right truncation

What does that mean?  Thanks!

--- In firebird-support@yahoogroups.com, "Allstars" <data@...> wrote:
>
> Hey it worked!! Thanks for the help! Really appreciate it!
> 
> --- In firebird-support@yahoogroups.com, "Allstars" <data@> wrote:
> >
> > Hello there, 
> > 
> > I am fairly new to FIREBIRD SQL.  I am using WINSQL as my database 
> > management system.
> > 
> > I am trying to insert into a table I created.
> > 
> > create table allBillOfMaterials(
> > 
> >   id int not null primary key
> > , totalTitles int not null
> > , bomNumber varchar(17) not null
> > , bomDescription varchar(255)
> > )
> > 
> > It creates the table and says (0) rows affected.  Fine.  I look at the 
> > database explorer and the table is there.
> > 
> > When i try to insert into the table, it says that the table is unknown. The 
> > id(pk) should be created automatically I'm thinking.  Someone save me!!
> > 
> > insert into allBillOfMaterials('', totalTitles, bomNumber, bomDescription)
> > select distinct
> > count(bom.num) as "Total"
> > ,bom.num as "BOM Number"
> > ,bom.description as "BOM Description"
> > from bom
> > inner join bomitem on bomitem.bomid = bom.id
> > inner join part on part.id = bomitem.partid
> > inner join bomitemtype on bomitemtype.id = bomitem.typeid
> > inner join customset on customset.recordid = part.id
> > where bomitem.typeid = 20
> > and customset.info = 'Book'
> > group by bom.num, bom.description
> > order by bom.description
> >
>


 

[Non-text portions of this message have been removed]

Reply via email to