GsRdbWriteStreams need schema or get #invalidTableErrors

When generating instances of the new GsRdbWriteStream class via these
methods:

    openInsertCursorOn:*
    openUpdateCursorOn:*
    openDeleteCursorOn:*

and the Oracle schema that contains the table is different from the
current schema of the current Oracle user, you will need to prefix the
table name with the schema, using standard Oracle schema naming conventions.

For example, if table MYTABLE was created by Oracle user BOB using
his default current schema (same as his user name: BOB), then for
Oracle user FRED to access it, he will need to use 'BOB.MYTABLE'
as the name of the table.

The fully qualified table name can be either passed directly to the
open*CursorOn:* method via the tableName: argument, or made part of the
table's associated #rdbTableName method definition.

Failure to properly qualify the table name with the schema when needed
will result in a GemConnect #invalidTableName error.

Workaround:

No workaround