Why does the V12 Help say "The -b option should not be used if you are using LOAD TABLE"?

I agree that -b might not help a lot if you are using LOAD TABLE, but "not help a lot" is quite different from "should not be used".

For example, consider an application that uses both INSERT and LOAD TABLE to load masses of data... the INSERT operations would benefit greatly from dbsrv12 -b (no giant transaction log).

Why should that application eschew dbsrv12 -b simply because it also uses LOAD TABLE?

http://dcx.sybase.com/index.html#1200en/dbadmin/b-database-dbengine.html

-b dbeng12/dbsrv12 server option

Uses bulk operation mode.

This option is useful for using the Interactive SQL INPUT statement to load large quantities of data into a database. See INPUT statement [Interactive SQL].

The -b option should not be used if you are using LOAD TABLE to bulk load data. See LOAD TABLE statement.

When you use this option, the database server allows only one connection by one application. It keeps a rollback log, but it doesn't keep a transaction log. The multi-user locking mechanism is turned off.

When you first start the database server after loading data with the -b option, you should use a new transaction log file.

Bulk operation mode doesn't disable the firing of triggers