Hundreds of characters.
My example concatenates a bunch of attributes like name and address together to
see if there are any matching records already on file, before creating a new
record. I set the alternate key length to 160 for this one index, and nothing
bad happened (so far).
I use that
Hey,
Just wondering how others have approached this - storing multi-byte names and
addresses for non-English languages.
I don't think we're approaching the demarcation line where an NLS
implementation would be warranted, with the Administrative overhead that
incurs. We are doing a lot more
We do store multi byte stuff, the biggest issues we have are not in the
storing but in its identification so that you can then transport and display
it correctly, we often get the data in xml files so we need to know that the
file has the correct character set definition, similarly the data is
End users are picky. They want to be able to send pretty formatted HTML
message bodies and mixed MIME multipart messages with Excel spreadsheets
and .pdf's and .jpgs' attached.
Symeon Breen wrote:
What could be simpler than the shell commands i gave examples of - why would
you complicate it
The pretty content is separate to the sending mechanism - you can create a
mime document in many ways and use the mutt or mail command to send it in
just the same manner.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf
Or sendmail and blat which is what I'm using.
My point is that using mutt as you describe sends whatever file you
specify as an attachment, not as the body of the message.
Symeon Breen wrote:
The pretty content is separate to the sending mechanism - you can create a
mime document in many
Ah ok I see
We usually generate an html email, mime encode it into a text file and do
something like
cat mimeFile | mail -s {subject} emailaddress
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Schasny
