diff options
| author | Ocke Janssen [oj] <Ocke.Janssen@sun.com> | 2009-11-16 09:59:12 +0100 |
|---|---|---|
| committer | Ocke Janssen [oj] <Ocke.Janssen@sun.com> | 2009-11-16 09:59:12 +0100 |
| commit | f448a7b94dafd3e80e7cfdc405e2dbccbfdef1d6 (patch) | |
| tree | b3d5bcb2ef2cb939f231d95d5c146fb8aa349a08 /connectivity/inc | |
| parent | cc423d4be4338cbd81eed9f96f7c7a277da0ee88 (diff) | |
| parent | 1e0bc426a966d9920714d0d3404ae32bdda9bdd7 (diff) | |
dba33d: pull from dba33b
Diffstat (limited to 'connectivity/inc')
| -rw-r--r-- | connectivity/inc/connectivity/dbmetadata.hxx | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/connectivity/inc/connectivity/dbmetadata.hxx b/connectivity/inc/connectivity/dbmetadata.hxx index 1ee1718247ae..4cfab247c10f 100644 --- a/connectivity/inc/connectivity/dbmetadata.hxx +++ b/connectivity/inc/connectivity/dbmetadata.hxx @@ -121,6 +121,17 @@ namespace dbtools */ bool supportsSubqueriesInFrom() const; + /** checks whether the database supports primary keys + + Since there's no dedicated API to ask a database for this, a heuristics needs to be applied. + First, the <code>PrimaryKeySupport<code> settings of the data source is examined. If it is <TRUE/> + or <FALSE/>, then value is returned. If it is <NULL/>, then the database meta data are examined + for support of core SQL grammar, and the result is returned. The assumption is that a database/driver + which supports core SQL grammar usually also supports primary keys, and vice versa. At least, experience + shows this is true most of the time. + */ + bool supportsPrimaryKeys() const; + /** determines whether names in the database should be restricted to SQL-92 identifiers Effectively, this method checks the EnableSQL92Check property of the data source settings, |