[geeklog-devel] postgresql and Geeklog 2.0.0b1
danstoner at gmail.com
Fri Jul 6 07:55:19 EDT 2012
I did not mean to suggest that the install script should be doing this.
Noting the prerequisites in the INSTALL doc or release notes might be
The script could be extra nice and check to see if the language is in the
database, and give a nice message rather than failing the SQL call (in the
same way the script notices if a database does not exist).
On Jul 5, 2012 9:39 PM, "Joe Mucchiello" <jmucchiello at yahoo.com> wrote:
> > "To create a database, you must be a superuser or have the special
> > CREATEDB privilege."
> > http://www.postgresql.org/docs/8.1/static/sql-createdatabase.html
> > "The user must have the PostgreSQL superuser privilege to register a
> > new language."
> > http://www.postgresql.org/docs/8.1/static/sql-createlanguage.html
> > When I create a new database for geeklog I am doing that step as a
> > Superuser.
> The Geeklog install script doesn't run the create database command in
> pgsql, mysql or mssql. It assumes the database is already created in order
> to avoid the problem of needing create database privilege. Most shared
> hosts provide a runnable script that creates databases outside of the
> normal admin programs for the database. (This is how they limit users to 1,
> 3, 5 or some other number of databases.)
> So perhaps instead the pgsql install just needs to check if the language
> is set on the database, attempt to create it if it isn't there, and failing
> that, explain what is needed to get it up and running. I really don't think
> Geeklog should take it on itself to modify "templates" in the database
> system. That is too far outside Geeklog's responsibilities to be mucking
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geeklog-devel