|
1 | 1 | # CDS database service for Postgres
|
2 | 2 |
|
3 |
| -Welcome to the new Postgres database service for [SAP Cloud Application Programming Model](https://cap.cloud.sap) Node.js, based on new, streamlined database architecture and [*pg* driver](https://www.npmjs.com/package/pg) . |
| 3 | +Welcome to the PostgreSQL database service for [SAP Cloud Application Programming Model](https://cap.cloud.sap) Node.js, based on streamlined database architecture and [*pg* driver](https://www.npmjs.com/package/pg) . |
4 | 4 |
|
5 | 5 | ## Setup
|
6 | 6 |
|
7 |
| -In general, all you need to do is to install one of the database packages, as follows: |
| 7 | +In general, all you need to do is to install the database package, as follows: |
8 | 8 |
|
9 | 9 | ```sh
|
10 | 10 | npm add @cap-js/postgres
|
@@ -38,7 +38,7 @@ Copyright 2023 SAP SE or an SAP affiliate company and cds-dbs contributors. Plea
|
38 | 38 | `@cap-js/postgres` works as a drop-in replacement for `cds-pg`.
|
39 | 39 | However, some preliminary checks and cleanups help:
|
40 | 40 |
|
41 |
| -- for using the BTP Postgres Hyperscaler as database, |
| 41 | +- for using the BTP Postgres Hyperscaler as database, |
42 | 42 | - know that the credentials are picked up automatically by from the enviornment (`VCAP_SERVICES.postgres`)
|
43 | 43 | - the service binding label is `postgresql-db`
|
44 | 44 | - `cds-dbm` is replaced by a hand-crafted "db-deployer" app → see below
|
@@ -134,11 +134,11 @@ now, re-use the CDS definitions: `SELECT.from(Beers).columns('brewery_ID').group
|
134 | 134 |
|
135 | 135 | So please adjust your `CQL` statements accordingly.
|
136 | 136 |
|
137 |
| -### timezones (potential _**BREAKING CHANGE**_) |
| 137 | +### timezones (potential **BREAKING CHANGE**) |
138 | 138 |
|
139 | 139 | any date- + time-type will get stored in [`UTC`](https://en.wikipedia.org/wiki/Coordinated_Universal_Time) **without any timezone identifier in the actual data field**.
|
140 | 140 | CAP's inbound- and outbound adapters take care of converting incoming and outgoing data from/to the desired time zones.
|
141 |
| -So when a `dateime` comes in being in [an ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) compatible format |
| 141 | +So when a `datetime` comes in being in [an ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) compatible format |
142 | 142 | `2009-01-01T15:00:00+01:00` (15:00:00 on January 1 2009 in Vienna (CEST))
|
143 | 143 | will get stored as
|
144 | 144 | `2009-01-01T13:00:00` (13:00:00 on January 1 2009 in UTC).
|
|
0 commit comments