From: Michael S. <msa...@pc...> - 2004-12-02 01:11:19
|
My comments below... Jeetendra Soneja wrote: > Hi all, > > The reason that I got errors that I posted earlier was that I did not do a > build. I had just created the Postgresql GUS schema and was trying to > register the gus application. However, after doing a build, things worked > out fine. > > I would like to list some of the problems that I have faced till this > point in using the Postgresql version:- > > -- The rows included in the script gus-rows.pl need a minor modification. > Values in the rows that are being inserted into core.databaseinfo need to > be changed. The names of the schemas CORE, DOTS and SRES should be changed > Core, DoTS, SRes respectively. Also the values for the version numbers > should be changed from 1.0 and 3.0 to 1 and 3 respectively. > Yes-- the object layer currently does string comparison (and purely just equality) between the version numbers. This needs to be resolved at some point... > -- Currently, I am having trouble registering a plugin (any plugin). A > number of modules/subroutines are retrieving row as a hash-reference and > access a value in a row using key, i.e. column name of the table. And all > the keys used in the code are in upper case. This works in case of oracle, > however, select statements in Postgresql return all the column names in > lower case. Therefore, in this case, it couldn't find the row for ga in > the core.algorithmimplementation table (although it's there since I have > already registered ga). And when I change the key/column name to lower > case in GusApplication.pm code, it worked fine. > I've sent updated DDL to the list to fix some of the capitalization issues, but you're right-- there are some larger issues that still exist. Unfortunately, some of these issues may have larger implications on the object layer. Thanks for your analysis-- this issue was the next on my list and it's really helpful. --Mike > I would appreciate any suggestion or comments. > > Thanks a lot, > Jeetendra. > > > > > >> >>Hi Jeetendra, >> >>Comments below.... >> >>Jeetendra Soneja wrote: >> >>>Hi Michael, >>> I am glad that the PostgreSQL version has been released. >>> >> >>This is not an official release!! These are preliminary scripts, which >>have had very little testing and are likely to change in the future >>(although probably not significantly). >> >> >>> I had a question about using it. Could you tell me if any of the >>>existing plugins (especially those in Common::Plugin) would work >>>with PostgreSQL version of GUS ? >>> >> >>No existing plugins have been tested with PGGUS. Please report any >>successes or failures you have to the list. >> >>--Mike >> >> >>>Thanks, >>>Jeetendra. >>> >>> >>> >>> >>> >>>>All, >>>> >>>>Postgres GUS scripts are attached. The first, pggus.sql contains DDL >>>>for creating GUS tables, indexes, constraints, and sequences. The >>>>second, gus-rows.sql, contains DML for populating the core.tableinfo and >>>>core.databaseinfo tables. >>>> >>>>Consider these early beta-- this is not part of an official release, >>>>they've had very limited testing, and they are unsupported. In general >>>>the existing documentation should provide the information needed to >>>>create an instance with these and GUS with it, but there are derivations >>>>that will be necessary. >>>> >>>>More information on Postgres and GUS, including an official release, >>>>should be coming in the next several weeks. >>>> >>>>Thanks, >>>> >>>>Mike >>>> >>>> >>>> >>> >>> >>> > > |