Alexei Novakov wrote: > > Hi, Elke > > Thank you for the prompt response. > > > > I found the information that SAPDB/MaxDB core > > doesn't > > > distinguish between char and varchar types. > > > > > > Where did you find this? > > In which context? > > I found this information when was having problem with > getting string values with trailing spaces from the > database. In my case all the trailing spaces were > trimmed. I did search in the internet and found that > many people had the same issue and one of responses > was that the core just doesn't distinguish between > char and varchar types. I was wondering if it affects > physical storage of the value. > > Best regards. > > Alexei. >
Ok, I see. This and Marcin P's mail belong together: As the kernel receives the data from the client with fixed length (not taking into account if it was defined as char or varchar) the kernel does not know if trailing blanks are there because of user's input or because the way of transport to the kernel or by extending the char-column to its full length during storing. Therefore, during 'reading' it truncates all leading blanks, for char and varchar. Elke SAP Labs Berlin > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
