Running install.php of Drupal on Ingres
Friday, November 6, 2009

There are a couple of things to be watch out for before you run the install script:

  • Make sure that you have enable the rewrite module in Apache. To do this, uncomment the following line in \\Apache\conf\httpd.conf
    #LoadModule rewrite_module modules/mod_rewrite.so

  • We need to make sure Drupal will be able to use the modules. To do so, make sure we have these variables set to the following values, if not, then change them:
    • Options Indexes FollowSymLinks
    • AllowOverride All,
    • Order allow,deny
    • Allow from all

  • Since it may take longer than 30 seconds to run the install.php, therefore, we'd better change the maximum execution time in the php.ini located in where the command php -i gives you, to the following line: max_execution_time = 120
  • Make sure that you have the database with the name drupal created in Ingres by the following command: createdb drupal. For Windows user, this will create a database namely drupal with the username system. The command: createdb -uyourusername drupal will create a database with the DBA -uyourusername. By default, for Windows user, createdb -uyourusername drupal, where yourusername is not your windows account name, then you need to type destroydb -usystem drupal or destroydb -uyourusername drupal to delete the database


While you are installing, you should
  • Put drupal as your database name
  • Put username system if your Apache is running as a service, otherwise, put the usename that you've set your apache to be running as.
  • There you go :)

Posted byA nerdy girl at 9:42 AM 0 comments  

Fix: Drupal on Ingres, install.php warnings
Wednesday, November 4, 2009

While running the install script of Drupal on Windows XP, I came across the following warnings.

warning: ingres_query() [function.ingres-query]: Error: 7 - Unable to close non-result resource statement in /some_path_of_mine_where_drupal_sits/

Here is a list of actions that you can try out to make the list of warnings go away:
  • You might want to make sure that you have entered the correct user name (user name that apache runs as). Follow this to check if your Apache is running as a service or locally. If it is running as a service, put system as the user name, otherwise, put the windows account user name.
  • You might want to destroydb/createdb again because error messages during install could mess with it.
  • You might find it takes forever to delete the database, try restarting apache and goes again.


If all these don't work, try consulting the IRC channel #ingres :)

Posted byA nerdy girl at 2:49 PM 0 comments  

Labels: , ,

Fix: Drupal on Ingres,Your web server does not appear to support any common database types.

As of date 2009-Nov-04, Ingres support has not been integrated into the main Drupal product yet.

So when you run install.php under Drupal, if you "Your web server does not appear to support any common database types." Checkout the code from Ingres: http://code.ingres.com/apps/drupal/trunk instead of getting from Drupal.org

Posted byA nerdy girl at 8:42 AM 0 comments  

Labels: ,

Basic sql tutorial in Ingres

Here you go!

Posted byA nerdy girl at 7:26 AM 0 comments  

Labels: , ,

Configuring Apache, PHP, Ingres on Windows Vista
Tuesday, November 3, 2009

After getting Apache, php, ingres talking to one and other, still no luck in letting Drupal know about Ingres. I need to identify the problem before another round of midterm marching up to me :(.

Today, I digged up another document for the sets of configuration for Apapche, Php, and Ingres for Windows Vista.

Posted byA nerdy girl at 4:21 PM 0 comments  

Labels: , , , ,

Fix: Errno 3502, no GRANT or GRANT compatible permit exists

aka, UCOSP: status report #12

Here is a piece of php code that I ran to check I can execute query under my web server.
There it prints this error message:

no GRANT or GRANT compatible permit exists


Reason:
By default, when you create a database, the access to the database is public.
By default, when you create a table/view/procedure the access is restricted to the owner.
You will need to do "grant select on the_table/view/procedure_you_want to public". For convenience, I did "grant all on test" and ran the code above. Remember you will NEED TO log off the database where that table is sitting in order for the above code to work :)

Posted byA nerdy girl at 10:32 AM 0 comments  

Labels: , , ,

Subscribe to: Posts (Atom)