FreeTDS Development Group

[Cedric ROUVRAIS <cedric.rouvrais AT sgcib.com>]

Hi James,

Thank you for your response, I would just like to respond to the
philosophical aspect whilst I look at the other points, if you don't mind
:o)

> You bring up an interesting philosophical point: are trailing spaces
data?
> IMO, no, they're not, and freebcp is correct not to pad character data.
> Evidently the authors of bcp thought otherwise, hence the tiny
> incompatibility

>From my perspective it depends on the data type. If we look at Sybase and
MS SQL BCP the behaviour depends on the datatype.

If you bcp out a column that is varchar() then the trailing spaces are
dropped, on the other hand if you bcp out a char(64) then the you get
exactly 64 characters in the file.

So, as I see it, in the case of a fixed column width, the trailing spaces
are data, otherwise I would use varchar() :o)

You can also simulate this behaviour by doing a select colA + colB + colC +
colD from someThing

You will see that in the case of fixed column width the trailing spaces are
preserved by the database.

Also, I am inclined to think that consistency is sometimes more appropriate
than correctness. As such, it would appear to me that the fact that freebcp
doesn't behave as the other bcp commands, would be a disadvantage more than
an advantage.

Just a thought.

By the way, it's not really a report writer, the downstream process
requires simili COBOL Copybooks (fixed width files and not delimited type
files). In this context, views/tables, are extremely handy and the database
is clearly more performant than anything else to process large volumes of
data in such a manner.

Regards,

Cedric


*************************************************************************
This message and any attachments (the "message") are confidential, intended 
solely for the addressee(s), and may contain legally privileged information.  
Any unauthorised use or dissemination is prohibited.  E-mails are susceptible 
to alteration.  Neither SOCIETE GENERALE nor any of its subsidiaries or 
affiliates shall be liable for the message if altered, changed or falsified.
*************************************************************************