Forum .LRN Q&A: Postgres dotlrn install question about Request Error.

1: Postgres dotlrn install question about Request Error.

Posted by Zachari Partridge on 08/01/02 08:51 PM

I don't see others having problems with this so I must have something configured differently/incorrectly but if anyone has any suggestions why the following request error appears during dotLRN installation I'd sure appreciate some suggestions or guesses. Thanks again, Zack.



Installing data model for dotLRN 1.0... 

Loading data model 
/web/EOR/packages/dotlrn/sql/postgresql/dotlrn-create.sql... 



Request Error

psql:users-init.sql:68: ERROR:  Function 'rel_segment__new(unknown, 
int4, unknown)' does not exist
        Unable to identify a function that satisfies the given 
argument types
        You may need to add explicit typecasts...

2: Response to Postgres dotlrn install question about Request Error. (response to 1)

Posted by Ben Adida on 08/06/02 05:21 PM

Zachari,

Can you give us a bit more info: version of OpenACS, version of PG, etc..?
Thanks!

3: Response to Postgres dotlrn install question about Request Error. (response to 1)

Posted by Zachari Partridge on 08/06/02 08:03 PM

Thanks for your response Ben, PG7.2 and what I think is OpenACS 4.5 (however I noticed the acs-kernel seems to have been update since my version was cvsed). I've just gotten back to this today. I cvsed everything again and created a new database. dotlrn installs w/o request errors. I did however need to cvs a number of packages individually from both openacs.org and the dotlrn site. Also just noticed that I can't add users or departments. I get request errors like


Selection did not return a value, and no default was provided
    while executing
"db_string select_node_id {}"
    (procedure "get_type_node_id" line 2)
    invoked from within
"get_type_node_id $parent_type"
    (procedure "dotlrn_community::new_type" line 4)
    invoked from within
"dotlrn_community::new_type  -community_type_key "$department_key"  
-parent_type "dotlrn_class_instance"  -pretty_name $pretty_name  
-description $desc..."
    ("uplevel" body line 2)
    invoked from within
"uplevel 1 $transaction_code "
    (procedure "db_transaction" line 1)
    invoked from within
"db_transaction {
            dotlrn_community::new_type  -community_type_key 
"$department_key"  -parent_type "dotlrn_class_instance"  
-pretty_name $pr..."
    (procedure "dotlrn_department::new" line 13)
    invoked from within
"dotlrn_department::new  -pretty_name $pretty_name  -description 
$description  -external_url $external_url"
    invoked from within
"if {[form is_valid add_department]} {
    form get_values add_department  pretty_name description 
external_url referer

    set department_key [dotlrn..."
    ("uplevel" body line 44)
    invoked from within
"uplevel {

Since this is a clean brand new installation I'm assuming the package is not completed yet? If it should be working and this is a bug let me know what other info I can provide to help track it down. Thanks again, Zack.

4: Response to Postgres dotlrn install question about Request Error. (response to 1)

Posted by Ben Adida on 08/06/02 08:18 PM

Zachari,

You can check things out easily by checking out dotlrn-core from the dotLRN
CVS. That gets you all the packages. That way you only have to do 2
checkouts for the whole thing. You should check out the detailed installation
instructions that explain this process.

Once you've done that, let us know if the bug remains (because this has been
fixed on PG 7.2 to our knowledge).

5: Response to Postgres dotlrn install question about Request Error. (response to 1)

Posted by Zachari Partridge on 08/06/02 09:00 PM

OK Thanks. It works now. (I needed to restart the server) Also all
packages cvs as you said - not sure why I didn't get them before
since I copy and paste the cvs command from my notes every time.

Zack.