Subject | Re: [firebird-support] Variable Data Field Size |
---|---|
Author | Daniel Albuschat |
Post date | 2008-10-22T08:42:52Z |
2008/10/22 Moegamat Alexander <alexanderm@...>:
you won't run into trouble when inserting binary data into one row and
textual data into the other. The database does not optimize anything
for text. What it does, however, is transliterate character sets for
you. But since you're storing ASCII (that is, 7bit) data anyways, this
is not an advantage to you.
Storing binary data as base64 is unneeded and you should really store
them as binary. Base64 does not give you an advantage in portability
whatsoever. For example, it does not solve endian-problems for you (if
any exist at all).
I'm storing arbitrary binary data in a database and have had no issues
at all with it.
Regards,
Daniel Albuschat
--
eat(this); // delicious suicide
> HiHey there,
>
> For one .. I understand mixing blobs with "other" data could have a
> performance impact and two perhaps i makes my solution
> kinda portable. I already have the solution working in postgresql as
> text/varchar data is kinda universal
you won't run into trouble when inserting binary data into one row and
textual data into the other. The database does not optimize anything
for text. What it does, however, is transliterate character sets for
you. But since you're storing ASCII (that is, 7bit) data anyways, this
is not an advantage to you.
Storing binary data as base64 is unneeded and you should really store
them as binary. Base64 does not give you an advantage in portability
whatsoever. For example, it does not solve endian-problems for you (if
any exist at all).
I'm storing arbitrary binary data in a database and have had no issues
at all with it.
Regards,
Daniel Albuschat
--
eat(this); // delicious suicide