google-code-export / s3db

Automatically exported from code.google.com/p/s3db
1 stars 0 forks source link

Problem updating the s3db_statement_log table. #41

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What is the URL of your deployment?
http://aleph.inesc-id.pt/s3db/

What steps will reproduce the problem?
1.Install s3db in linux supported by postgres 
2. insert a statement
3.

What is the expected output? What do you see instead?
Expected s3db_statement_log table to be updated.
I see in postgresql error log:
ERROR:  invalid input syntax for integer: ""
STATEMENT:  insert into s3db_statement_log (statement_log_id, statement_id,
old_rule_id, old_resource_id, old_project_id, old_value, old_notes, action,
modified_by, modified_on, created_on, created_by) values ('', '34649',
'29048','34636','3628','NUMBER','','create','3510', now(), '', '3510')

What version of the product are you using? On what operating system?
3.5.7 on the last beta update (see pic). linux.

Please provide any additional information below.

The field type "timestamp" in postgres, does not except strings.
in the error log, the field created_on is being filled with '',
which represents a string.

Further I think the problem is conceptual. the audit trail table only
has to accept "modified date". the first modified date of a statement,
that appears in s3db_statement_log is actually the created_on date...
 therefore created_on and created_by are redundant fields in this table,
in my opinion.

Original issue reported on code.google.com by mdsaT...@gmail.com on 16 May 2010 at 9:48

Attachments: