The below is a cut and paste.   It shows a table with the name 

Sys_comment_id and a column of Sys_comment_id. 



When I unloaded the database structure, the below is included 

in the output file as well: 


CREATE TABLE `SYS_COMMENT_ID`  + 
(`SYS_COMMENT_ID` INTEGER  ) 


Unless I hear otherwise, I am going to remove this table manually 

and see what happens. 



Thanks 

-Bob 







----- Original Message ----- 
From: "Alastair Burr" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Monday, January 24, 2011 10:58:39 AM 
Subject: [RBASE-L] - Re: Corrupt or invalid table 




CREATE TABLE `SYS_COMMENT_ID`  + 
(`SYS_COMMENT_ID` INTEGER  ) 


Unless I hear otherwise, I am going to remove this table manually 

and see what happens. 



Thanks 

-Bob 







----- Original Message ----- 
From: "Alastair Burr" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Monday, January 24, 2011 10:58:39 AM 
Subject: [RBASE-L] - Re: Corrupt or invalid table 




SYS_COMMENT_ID is a valid column in the SYS_COMMENTS table. 

SYS_COMMENT is the other column in the table. 

Are you sure that you are seeing what you think you are seeing? 

Your SYS_COMMENTS table may be empty if you never add comments to your table 
definitions. 

Regards, 
Alastair 





From: [email protected] 
Sent: Monday, January 24, 2011 2:57 PM 
To: RBASE-L Mailing List 
Subject: [RBASE-L] - Corrupt or invalid table 




I seem to have a corrupt or invalid table in my database. 

R>list table sys_comment_id 

   Table: SYS_COMMENT_ID       No Lock(s) 

   Triggers: 
No. Column Name        Attributes 
--- ------------------ ------------------------------------------------------ 
   1 SYS_COMMENT_ID     Type   : INTEGER                                      
                        Index  : SINGLE-COLUMN                                
   Current number of rows:      0 



I am assuming that this "sys_comment_id" table is not correct. 



I had a database corruption last week and another this morning.  I 

suspect it has to do with something related to this possibly errant table. 



Seems like I have seen this on the list sometime in the distant past. 

(version 7.5) 



Any suggestions? 



Thanks, 



Bob

Reply via email to