From: Chris S. <sto...@pc...> - 2005-07-29 16:52:57
|
After conferring with Mike, it appears that this happens for only a couple tables. Our choices are: - set default values (which can be done for Oracle or Postgres) - make the Plugins handle this. - make these nullable My inclination is to make the plugins handle this because it eliminates special cases (i.e. default values for a couple tables) and can be implemented immediately. Unless I hear a strong argument to convince me otherwise in the next week this will be considered resolved. Chris On Jul 19, 2005, at 12:24 AM, Mark S. Heiges wrote: > ApiComplexa::DataLoad::Plugin::dbEST is the same as > GUS::Community::Plugin::dbEST (recently renamed to > LoadFromdbESTMirror.pm) except it reads from a remote database link > to Penn's dbEST mirror. > > With GUS 3.5 it throws the error > cannot insert NULL into > ("DOTS"."NASEQUENCEIMP"."SEQUENCE_VERSION") > > This error is clear enough but this was not a problem in GUS 3.0 > where sequence_version would always get set to '1'. > Sequence_version doesn't seem to get set by dbEST so apparently > there is some default assignment elsewhere. Checking a GUS3.0 > Oracle instance, there appears to be a default value defined in the > NaSequenceImp table definition that I don't have in my 3.5 instance. > > Does sequence_version need to be explicitly set by plugins for 3.5 > or is my 3.5 NaSequenceImp table erroneously missing a default > value for that column? > > > -M > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Gusdev-gusdev mailing list > Gus...@li... > https://lists.sourceforge.net/lists/listinfo/gusdev-gusdev > |