> -----Original Message----- > From: frank_lupo [mailto:[EMAIL PROTECTED] > Sent: 06 March 2003 14:41 > To: Dave Page > Cc: pgadmin-hackers > Subject: Re: [pgadmin-hackers] reindex action > > > > > > > > > -----Original Message----- > > > From: frank_lupo [mailto:[EMAIL PROTECTED] > > > Sent: 05 March 2003 21:13 > > > To: pgadmin-hackers > > > Subject: [pgadmin-hackers] reindex action > > > > > > > > > I developed a reindex command (table,index no database). > > > > Sorry Frank - this breaks the OO design of pgSchema. Unless > there are > > exceptional circumstances, anything that occurs to an > object should be > > implemented as a method of that object, so I would expect to see > > methods > > like: > > > > pgIndex.ReIndex() > > pgDatabase.ReIndex() > > pgTable.ReIndex() > > > > Can you recode it in that fashion please? > > > > Thanks, Dave. > > > > Excuse, I have corrected the schema.
Looks good. > How we make to call these actions? In basActions.bas, you need a Reindex() sub which will be similar to Drop(). In there, check the object type, and if appropriate call the reindex method eg: ctx.CurrentObject.ReIndex In clsContext, there needs to be code to enable/disable the reindex option in Property Set CurrentObject/CurrentDB. Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
