validity of the result. Base64 encoding intentionally results in primitive
data (a string) so it can be used wherever primitive data can go
(particularly emails). The price for that benefit is that you have to do a
little extra bookkeeping to track whether stuff is encoded or not.
Cheers,
barneyb
> -----Original Message-----
> From: Chunshen (Don) Li [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 01, 2004 3:41 PM
> To: CF-Talk
> Subject: Re: Function for data type determination
>
> >I would guess that your best bet is to store some metadata about the
> >content -- maybe a "binary vs. text" flag or something.
> Ben,
>
> That's not an option. What if the database is not mine (I
> don't have control over its structure or the like). My
> thought was, if you/MM have a way/algorithm, that is, BASE64
> to convert binary data, you should also know if a set of data
> has been "BASE64"ed with the same algorithm in a reverse
> fasion, so, a function like IsBase64 would be very helpful.
>
>
> >Ah. Sorry. I thought you were using "simple data" in a
> technical sense.
> >
> >As far as I know, there's not really a good way to do this.
> After all,
> >"IBM +3.75 6% 14-3/8" would make sense to some people (well,
> it would if
> >it were really a stock quote), but doesn't fit the "English
> or Number"
> >model.
> >
> >On the other hand, it is technically possible for an image
> (for example)
> >to convert to an integer in Base64.
> >
> >I would guess that your best bet is to store some metadata about the
> >content -- maybe a "binary vs. text" flag or something.
> >
> >I know that doesn't really answer your question, but I hope
> it helps anyway.
> >
> >--Ben Doom
> >
> >Chunshen (Don) Li wrote:
> >
> >>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
