[SQL] Wierd Error on update
Hi All, I am relative PostGres newbie, so if there is a simple answer to this question, please feel free to send me a link or explaination. I am running Postgres 7.3 on a intel Linux Redhat 7.3 base. I am getting two errors which are a bit confounding. ERROR: pg_class_aclcheck:relation 474653086 not found on one table within a large SQL file update (+5000 lines with documentation) that needs to be run from the command line. Both statements are multiline Update statements. This is straight SQL, not function code. Now I can guareentee that the queries refer to an existing table, but the table is being rebuilt in the core of the long SQL update. The table in question now has all permissions (my attempt to get fixed, but that did not help). Interesting aspect to this problem is that if your run the large update in one file, and then run the two update statements in a second file it works fine. Now I placed the erroring statements at the end of the large file to make sure it was not a ordering error, but that didnt help. Any ideas? Thank you Thomas Seeber ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [SQL] Wierd Error on update
> Original 7.3 release, or (I hope) 7.3.something? Red Hat 7.3.2.96-113 Linux Version 2.4.20-20.7custom from cat /proc/version > > I am getting two errors which are a bit confounding. > > ERROR: pg_class_aclcheck:relation 474653086 not found > > Are there any views involved? No views. Is the statement invoking any functions? The statement is not invoking any fuctions However heres the statements, UPDATE school_info_l SET ind_default_data = 't'; UPDATE school_info_l SET sis_system_id = 9 where school_id IN (492, 434, 436); which are amazingly simple. Both queries return the same exact error, same error. not your > How about triggers? Foreign keys? Rules? Neither of the updates touch any rules. sis_system_id has a foreign key constaint to another table that does in it contain a value of 9 for sis_system_id in that table, but the first isnt touching anything that has a trigger or foreign key constraint attached to the column. The table school_info_l has many contraints that affect other tables however > Also, is it always the same number in the error, or does that change > from run to run? The number is the same for each time I run the update file on the same database. with this two queries having the same error. Same result to, if I run these two after the first update file finishes there is no problem, but if I try to run it at the end of hte first file, choke. Very Odd problem to me, since the update statemenets are so simple. -Tom ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[SQL] Postgres 7.3 migrate to 8.0 date problems.
Hi, We were upgrading from postgres 7.3 -> 8.0 and having a little problems importing dates from some of our data sources. Say we have a date like '2004-17-05'. In postgres 7.3, postgres would intrept this as Year Day Month automatically. In the documentation, from postgres 7.4 on this has to be specified in the Datestyle option and YDM is not an option. Other data we have is coming in on the YMD formate which would be more expected. I realize that this change is better for data integrity, however we have alot of legacy systems where being able to mimic the 7.3 behaviour would be desireable. Any ideas? -Tom Seeber Edison Schools ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
