Re: bug report - linefeeds and PGP encrypted mv_credit_card_info

[Brian Bullen <b.m.bullen@stir.ac.uk>]

On Sat, 10 Jul 1999 mikeh@minivend.com wrote:

> Quoting Brian Bullen (b.m.bullen@stir.ac.uk):
> > 
> > The mv_credit_card_info after PGP encryption contains multiple lines
> > 
> > This is OK in the session database, but when stored in the userdb
> > the NL are lost.
> 
> They aren't lost when stored, but they are lost when exported. After
> all, we have to change newline to something unless you want the
> import not to be readable. There is a CONTINUE UNIX capability, but
> the exporter doesn't honor that.
> 
> If you re-import the DB after exporting (which you normally should not
> do in UserDB) then you will see this.
> 
> I felt the least intrusive policy on an export/import was to use the
> mac-style carriage return only. Suggestions are welcome, but this is a
> hard one that has yet to be fully cracked by anyone that I know of.

Thanks, of course ! I had exported when moving the userdb into a SQL
database.
Perhaps the minivend NOTES database format would be appropriate 
if it is necessary to import/export - many of the userdb fields
are blank for most users so the overhead of the field names
is not excessive,  and using LF as the record delimited
allows the credit_card_info to contain NL chars.

A related issue - the default datatype for the userdb 'code'
field is char(16) -- several of our customers want to use their email
address as their login name, so can the 'code' field be (say) char(128) -
would this be a problem ?
Regrds
Brian