Ok, I now got some kernel traces:
This is from the MaxDB 7.5 database running on the Windows machine when using the
Windows ODBC driver:
REQUEST: ascii, full_swap, 70500-ODB (1 segment, len: 152)
(13.5186 page 13)
parse SEGMENT 1 (1 part, len: 152)
internal, user_cmd
commit_immediately
command PART (1 argument, size: 32232)
buf(95):
494E5345 52542049 4E544F20 7469636B 65745F66 69656C64 5F757365
72736967 68742056 414C5545 5328302C 31343130 2C312C31 30373732
38323235 322C277A 65696C65 0D0A6E65 7565207A 65696C65 0D0A0D0A
6C656572 7A65696C 652729
'INSERT INTO ticket_field_usersight VALUES(0,1410,1,1077282252'
','zeile..neue zeile....leerzeile')'
I can see, that the newlines (\r\n because it was a windows client which entered the
data) are stored correctly (0D0A (Hex for \r\n)
in the line before the last line).
Same query with the linux ODBC driver and iODBC to the linux database:
REQUEST: ascii, full_swap, 70403-ODB (1 segment, len: 152)
(1.2919 page 2)
parse SEGMENT 1 (1 part, len: 152)
internal, user_cmd
commit_immediately
command PART (1 argument, size: 32552)
buf(95):
'INSERT INTO ticket_field_usersight VALUES(0,1410,1,1077282252'
','zeile neue zeile leerzeile')'
No hex output here, I wonder why...
Same query with the windows ODBC driver to the linux database:
REQUEST: ascii, full_swap, 70500-ODB (1 segment, len: 152)
(1.2415 page 2)
parse SEGMENT 1 (1 part, len: 152)
internal, user_cmd
commit_immediately
command PART (1 argument, size: 32552)
buf(95):
494E5345 52542049 4E544F20 7469636B 65745F66 69656C64 5F757365
72736967 68742056 414C5545 5328302C 31343130 2C312C31 30373732
38323235 322C277A 65696C65 0D0A6E65 7565207A 65696C65 0D0A0D0A
6C656572 7A65696C 652729
'INSERT INTO ticket_field_usersight VALUES(0,1410,1,1077282252'
','zeile..neue zeile....leerzeile')'
Here again the newlines are all there.
I included the complete traces for the linux->linux and the windows->linux setup
because they only differ in the OS the query is
coming from.
Regards
Uli St�rk
> -----Original Message-----
> From: Ulrich St�rk [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 20, 2004 2:01 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Newlines
>
>
> I already tried a SQL trace using the ODBC driver's tracing
> capabilities but all it seems to trace are UPDATE and SELECT
> statements,
> no INSERTs.
> I'm no waiting for DBM rights for the database.
>
> Thanks so far.
>
> Uli St�rk
>
> > -----Original Message-----
> > From: Dittmar, Daniel [mailto:[EMAIL PROTECTED]
> > Sent: Friday, February 20, 2004 1:19 PM
> > To: 'Ulrich St�rk'; [EMAIL PROTECTED]
> > Subject: RE: Newlines
> >
> >
> > > But I'm wondering why the same thing works on a windows platform.
> >
> > Using http://sapdb.2scale.net/moin.cgi/ODBCTrace or
> > http://sapdb.2scale.net/moin.cgi/VTrace, one > could have a
> > look at what actually does get sent to the kernel.
> >
> > Daniel Dittmar
> >
> > --
> > Daniel Dittmar
> > SAP Labs Berlin
> > [EMAIL PROTECTED]
> >
>
>
> --
> MaxDB Discussion Mailing List
> For list archives: http://lists.mysql.com/maxdb
> To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
>
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
