hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dyozie <...@git.apache.org>
Subject [GitHub] incubator-hawq-docs pull request #86: HAWQ-1263 - misc doc updates
Date Mon, 16 Jan 2017 23:07:34 GMT
Github user dyozie commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96317322
  
    --- Diff: markdown/ddl/ddl-database.html.md.erb ---
    @@ -2,77 +2,75 @@
     title: Creating and Managing Databases
     ---
     
    -A HAWQ system is a single instance of HAWQ. There can be several separate HAWQ systems
installed, but usually just one is selected by environment variable settings. See your HAWQ
administrator for details.
    -
    -There can be multiple databases in a HAWQ system. This is different from some database
management systems \(such as Oracle\) where the database instance *is* the database. Although
you can create many databases in a HAWQ system, client programs can connect to and access
only one database at a time — you cannot cross-query between databases.
    +Your HAWQ deployment may have multiple databases. This is different from some database
management systems \(such as Oracle\) where the database instance *is* the database. Although
you can create many databases in a HAWQ system, client programs can connect to and access
only one database at a time — you cannot cross-query between databases.
     
     ## <a id="topic3"></a>About Template Databases 
     
    -Each new database you create is based on a *template*. HAWQ provides a default database,
*template1*. Use *template1* to connect to HAWQ for the first time. HAWQ uses *template1*
to create databases unless you specify another template. Do not create any objects in *template1*
unless you want those objects to be in every database you create.
    +Each new database you create is based on a *template*. HAWQ provides a default database,
`template1`. HAWQ uses `template1` to create databases unless you specify another template.
Do not create any objects in `template1` unless you want those objects to be in every database
you create.
     
    -HAWQ uses two other database templates, *template0* and *postgres*, internally. Do not
drop or modify *template0* or *postgres*. You can use *template0* to create a completely clean
database containing only the standard objects predefined by HAWQ at initialization, especially
if you modified *template1*.
    +HAWQ uses two other database templates internally, `template0` and `postgres`. Do not
drop or modify `template0` or `postgres`. You can use `template0` to create a completely clean
database containing only the standard objects predefined by HAWQ at initialization, especially
if you have modified `template1`.
    --- End diff --
    
    ", especially if you have modified `template1`" -> ". This may be necessary if you
have modified `template1`."
    
    This also implies that template0 and template1 are the same - is that correct?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message