Skip to content

Commit

Permalink
Updated README to describe nested document field changes.
Browse files Browse the repository at this point in the history
  • Loading branch information
Ozgun Erdogan committed Jan 22, 2013
1 parent c4b0189 commit 5da5861
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -75,14 +75,14 @@ OPTIONS (database 'test', collection 'customer_reviews');
Limitations
-----------

* mongo_fdw currently can't reach into nested BSON documents. We can overcome
this limitation by interpreting the period character in column names as a
separator, and recursing into the BSON document for each separated key name.

* mongo_fdw currently can't access BSON document keys that have upper-case
letters in them. This is because column names in SQL are case insensitive. We
can overcome this limitation by having an option for each column name, where
the option value is case sensitive.
* If the BSON document key contains upper-case letters or occurs within a nested
document, mongo_fdw requires the corresponding column names to be declared in
double quotes. For example, a nested field such as "review": { "Votes": 19 }
should be declared as "review.Votes" INTEGER in the create table statement.

* Please note that PostgreSQL limits column names to 63 characters by default.
If you need column names that are longer, you can increase the NAMEDATALEN
constant in src/include/pg_config_manual.h, compile, and reinstall.

* mongo_fdw only incorporates the document count and average document size when
estimating costs for the query execution plan. A better estimate also includes
Expand Down

0 comments on commit 5da5861

Please sign in to comment.