topic Re: Comparing string field in Application Development and Automation Discussions

Comparing string field

Former Member — Fri, 16 May 2008 12:27:27 GMT

Hi,

If we are using a string variable 4000 length in a db table..

which will be like follows :

apid int 6

prid int 6

text string 4000

Second database design:

apid int 6

prid int 6

lines int 4

text 70

In first DB we will store all the characters from a text editor,concatenate and put in to tht field..Here it is in 1 record.

In second DB if there are 10 lines in Text editor am putting it as ten lines in database so it will be 10 records..

For retrieving and inserting whcih Databse design will be good in all circumstances(performance,speed etc.,)

Re: Comparing string field

Former Member — Fri, 16 May 2008 13:11:40 GMT

hi,

I think 2nd will be more usefull.

because the maximum length allowed for a field is 251.

so you can not exceed this size.

so go for the second one

Re: Comparing string field

Former Member — Fri, 16 May 2008 13:23:53 GMT

Hi,

If you use type string, the db use only the length oh this string.

And it is easier to develop and maintenance because you do not need you concatenate the fields.

So I think first is better.

Regards,

Fernando

Re: Comparing string field

Former Member — Fri, 16 May 2008 13:51:18 GMT

If you want SE16 to be useful on your table, you have to go with design #2. Yes, this design involves splitting while storing and concatenating when retrieving.

If you don't need SE16's services, consider using SAP's design used to store long texts.

Re: Comparing string field

Former Member — Fri, 16 May 2008 14:05:38 GMT

hi check this..

splitting the records is also come want complex because for every record u created there is some memory associated and if u split a record into 10 records then it will take more memory ....please ask the basis people for this..

regards,

venkat