To do that it provides own methods to write primitive Java types in specified number of bytes – for example an integer is written using 4 bytes. Random Access File is a separate class that allows to jump around the file and it doesn’t implement Input Stream nor Output Stream interfaces, so cannot be combined with other stream processing classes from Random Access File takes access permission as a constructor parameter. The actual batch is broken up into pieces this large that are sent separately.The reason for this is to avoid Sybase "hangs" caused by running out of space with very large batches.Either use a file stream that allows you to both read and write to the file - i.e.Random Access File or (more simply) write to a new file then replace the old file with the new one In psuedo code: Use Random Access file to write into specific place of the file.
Controls how many statements are sent to the server in a batch.Note that because the previous program will have written as unicode, if you create a text file with an editor containing a a string such as "Hello" , the following code will probably print out junk such as question marks.The Random Access File class is way out on it's own and doesn't fit neatly with the Stream I/O classes.I suspect this is because a character is 16 bits and because ASCII is 8 bit, the upper 8 bits result in a blank character.This also illustrates the previous objective in that it uses the Filter Output Stream descendent Data Output Stream. If this example only used File Output Stream methods you would be limited to writing bytes or ints.
The problem doesn't seem to occur with SQL Server, hence the default limit of 0 (unlimited) in this case.