On Sun, 3 Feb 2013 14:31:06 -0800 Pawel Aleksander Fedorynski <pfe...@gmail.com> wrote:
PAF> On Sun, Feb 3, 2013 at 2:26 PM, Vadim Zeitlin <vz-s...@zeitlins.org> wrote: PAF> PAF> > On Sun, 3 Feb 2013 14:17:49 -0800 Pawel Aleksander Fedorynski < PAF> > pfe...@gmail.com> wrote: PAF> > PAF> > PAF> It occurs to me that some other db engines (Oracle?) probably send PAF> > values PAF> > PAF> in non-string format, what should into_as_raw_text() do then? PAF> > PAF> PAF> > PAF> (a) signal an error? PAF> > PAF> PAF> > PAF> (b) put the raw value (which may be non-printable and may be packed PAF> > in some PAF> > PAF> unobvious way) in the provided string, say the value is of type INT32 PAF> > and PAF> > PAF> some db sends four bytes over the wire, should we put these exact four PAF> > PAF> bytes into the string? PAF> > PAF> PAF> > PAF> (c) convert to string? PAF> > PAF> > I'd say (b). "Raw" would seem to mean this, i.e. exactly the bytes PAF> > received. PAF> PAF> Yes, I was thinking the same thing. But then it shouldn't be raw_text, PAF> raw_string maybe or raw_bytes even? Yes, taking this into account, into_raw_bytes() or maybe into_raw_buffer() (just because "buffer" is something you can put things into, while "bytes"... not so much IMHO) does seem better, thanks! VZ
pgpWbBaakoeM3.pgp
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________ soci-users mailing list soci-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/soci-users
