![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi NG, I have a very general question concerning the XML-abilities oracle offers, and I'm afraid I cannot restrict the field of possible causes for this kind of error: When performing a query where an XMLType is returned, in some cases 4 or 8 bytes are written before the prologue. Did anyone else observe this behaviour, what does these characters stand for and how can I get a grip on this? thx, Albert |
#3
| |||
| |||
|
|
Hi NG, I have a very general question concerning the XML-abilities oracle offers, and I'm afraid I cannot restrict the field of possible causes for this kind of error: When performing a query where an XMLType is returned, in some cases 4 or 8 bytes are written before the prologue. Did anyone else observe this behaviour, what does these characters stand for and how can I get a grip on this? thx, Albert |
#4
| |||
| |||
|
|
Hi NG, I have a very general question concerning the XML-abilities oracle offers, and I'm afraid I cannot restrict the field of possible causes for this kind of error: When performing a query where an XMLType is returned, in some cases 4 or 8 bytes are written before the prologue. Did anyone else observe this behaviour, what does these characters stand for and how can I get a grip on this? thx, Albert |
#5
| |||
| |||
|
|
Hi NG, I have a very general question concerning the XML-abilities oracle offers, and I'm afraid I cannot restrict the field of possible causes for this kind of error: When performing a query where an XMLType is returned, in some cases 4 or 8 bytes are written before the prologue. Did anyone else observe this behaviour, what does these characters stand for and how can I get a grip on this? thx, Albert |
![]() |
| Thread Tools | |
| Display Modes | |
| |