Attributes (MMBase 1.9-SNAPSHOT

java.lang.Object
- org.mmbase.storage.implementation.database.Attributes

```
public final class Attributes
extends Object
```
This class defines the attributes names used by the default database storage manager classes. Specific storage managers may ignore or add their own attributes.

Since:

MMBase-1.7

Version:

$Id$

Author:

Pierre van Rooden

Field Summary

Fields
Modifier and Type	Field and Description
`static String`	`BINARY_FILE_PATH` Attribute: `database-binary-file-path`.
`static String`	`DATA_SOURCE` Attribute: `database-data-source`.
`static String`	`FORCE_ENCODE_TEXT` Option: `database-force-encode-text`.
`static String`	`LIE_CP1252` If the database is ISO-8859-1, then you can switch this option to true, to store CP1252 in it.
`static String`	`REMOVE_EMPTY_DEFINITIONS` Option: `database-remove-empty-definitions`.
`static String`	`SEQUENCE_BUFFER_SIZE` Option: `sequence-buffer-size`.
`static String`	`STORES_BINARY_AS_FILE` Option: `database-stores-binary-as-file`.
`static String`	`SUPPORTS_BLOB` Option: `database-supports-blob`.
`static String`	`SUPPORTS_COMPOSITE_INDEX` Option: `database-supports-composite-index`.
`static String`	`SUPPORTS_DATA_DEFINITION` Option: `database-supports-data-definition`.
`static String`	`SUPPORTS_FOREIGN_KEYS` Foreign keys can be used
`static String`	`SUPPORTS_TRANSACTIONS` Option: `database-supports-transactions`.
`static String`	`TRANSACTION_ISOLATION_LEVEL` Attribute: `database-transaction-isolation-level`.
`static String`	`TRIM_STRINGS` Option: `trim-strings`.

Constructor Summary

Constructors
Constructor and Description

Attributes()

Constructors
Constructor and Description
`Attributes()`

Method Summary
- Methods inherited from class java.lang.Object
  clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Field Detail
  - DATA_SOURCE
```
public static final String DATA_SOURCE
```
    Attribute: database-data-source. The data source object used by the storage layer. This attribute is set by the storagelayer and returns a javax.sql.DataSource object. You should not set or configure this attribute (but you can retrieve it).
    
    See Also:
    
    Constant Field Values
  - SUPPORTS_TRANSACTIONS
```
public static final String SUPPORTS_TRANSACTIONS
```
    Option: database-supports-transactions. When true, the database supports transactions. The default is determined form the database, but you can override it.
    
    See Also:
    
    Constant Field Values
  - STORES_BINARY_AS_FILE
```
public static final String STORES_BINARY_AS_FILE
```
    Option: database-stores-binary-as-file. When true, binary data is stored on disk, rather than in the database. If you set this option ou should also set the attribute BINARY_FILE_PATH The default is false
    
    See Also:
    
    Constant Field Values
  - BINARY_FILE_PATH
```
public static final String BINARY_FILE_PATH
```
    Attribute: database-binary-file-path. The path to the directyory where binary files are to be stored if STORES_BINARY_AS_FILE is true. The default is the WEB-INF/data directory of the mmbase web application. Note that if you specify a relative url, it is taken from the web application's webroot.
    
    See Also:
    
    Constant Field Values
  - FORCE_ENCODE_TEXT
```
public static final String FORCE_ENCODE_TEXT
```
    Option: database-force-encode-text. If true, the database layer will explicitly decode/encode strings using the MMBase encoding when storing and retrieving text from the database. The default is false
    
    See Also:
    
    Constant Field Values
  - LIE_CP1252
```
public static final String LIE_CP1252
```
    If the database is ISO-8859-1, then you can switch this option to true, to store CP1252 in it.
    
    See Also:
    
    Constant Field Values
  - SUPPORTS_BLOB
```
public static final String SUPPORTS_BLOB
```
    Option: database-supports-blob. When true, the driver/database used supports the JDBC getBlob() method. The default is false
    
    See Also:
    
    Constant Field Values
  - SUPPORTS_COMPOSITE_INDEX
```
public static final String SUPPORTS_COMPOSITE_INDEX
```
    Option: database-supports-composite-index. When true, the database uses composite indices for 'key' fields. When false, it uses single indices (a separate index for each field) The default is true
    
    See Also:
    
    Constant Field Values
  - SUPPORTS_FOREIGN_KEYS
```
public static final String SUPPORTS_FOREIGN_KEYS
```
    Foreign keys can be used
    
    Since:
    
    MMBase-1.9.6
    
    See Also:
    
    Constant Field Values
  - TRANSACTION_ISOLATION_LEVEL
```
public static final String TRANSACTION_ISOLATION_LEVEL
```
    Attribute: database-transaction-isolation-level. The transaction isolation level used for connections to the database. This determines the level of transaction support. The default is determined from the database metadata.
    
    See Also:
    
    Constant Field Values
  - SUPPORTS_DATA_DEFINITION
```
public static final String SUPPORTS_DATA_DEFINITION
```
    Option: database-supports-data-definition. If true, the data definiton (table structure) can be changed using ALTER TABLE statements. Some databses (such as Informix) may have trouble with ALTER TABLE statements on OO-tables. Turn this option false for tehse databses. The default is true
    
    See Also:
    
    Constant Field Values
  - REMOVE_EMPTY_DEFINITIONS
```
public static final String REMOVE_EMPTY_DEFINITIONS
```
    Option: database-remove-empty-definitions. If this option is true, empty parenthesis in a table definition are removed. When you create a new table that extends form another table, but which doesn't add fields, you may get a statement that looks like:
    CREATE TABLE table1 () UNDER table2
    This statement will fail udner a database such as Informix, which does not accept empty parenthesis, but instead expects:
    CREATE TABLE table1 UNDER table2
    On the other hand, a database such as Postgresql DOES expect the parenthesis (and fails if they are ommitted.) The default is false
    
    See Also:
    
    Constant Field Values
  - SEQUENCE_BUFFER_SIZE
```
public static final String SEQUENCE_BUFFER_SIZE
```
    Option: sequence-buffer-size. The sequence buffer size is the number of keys that MMBase caches in the storage layer. You can use this to minimize the nr of times MMBase accesses the database to generate a new object number. When not set, the value is assumed to be 1.
    
    See Also:
    
    Constant Field Values
  - TRIM_STRINGS
```
public static final String TRIM_STRINGS
```
    Option: trim-strings. Some text fields for some databases need to be trimmed. The default is false
    
    See Also:
    
    Constant Field Values
- Constructor Detail
  - Attributes
```
public Attributes()
```

Class Attributes

Field Summary

Constructor Summary

Method Summary

Methods inherited from class java.lang.Object

Field Detail

DATA_SOURCE

SUPPORTS_TRANSACTIONS

STORES_BINARY_AS_FILE

BINARY_FILE_PATH

FORCE_ENCODE_TEXT

LIE_CP1252

SUPPORTS_BLOB

SUPPORTS_COMPOSITE_INDEX

SUPPORTS_FOREIGN_KEYS

TRANSACTION_ISOLATION_LEVEL

SUPPORTS_DATA_DEFINITION

REMOVE_EMPTY_DEFINITIONS

SEQUENCE_BUFFER_SIZE

TRIM_STRINGS

Constructor Detail

Attributes