Hi, This seams to be more a sybase issue but I have just been having the same conversation relating SQL Server.
In SQL Server this is related to being able to create tables that have variable length fields whos total size is larger than the page size. This results in tables where one varchar field works fine at max length but filling all the fields up to there max results in the error as the record no longer fits in a single page. Hope this helps Paddy On Mon, Jul 07, 2003 at 12:22:55PM -0000, Raf wrote: > > I saw this post, which doesn't appear to have been followed up: > > http://lists.ibiblio.org/pipermail/freetds/2002q1/006299.html > > I have the same problem: > > Where: > (4) attribute_value varchar(350) NOT NULL > > =head2 MyError > > 1> insert into attributes_string ( > object_id,attribute_id,object_insert_id,attribute_value,creation_time,modification_time,modified_by > ) values (18, 75, 7236, > 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa' > ,'2003/07/01', '2003/07/01',2) > 2> go > Msg 103, Level 15, State 1: > Server 'pelican', Line 1: > The identifier that starts with 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa' is too > long. Maximum length is 30. > > =cut > > This crashed my transaction and is giving me the same result in isql and > via DBD::Sybase. > > I know that it's not dbi specific , however it works when I reduced the > string "a"x350 to "a"x10. Given that the field is varchar(350) I really > don't get this? > > I've just moved to sybase from postgrest,sql,oracle and wonder if this > error is familiar to other developers? > > Cheers, > > Raf > > > >
