Its not really a failure, and the cite engine is probably the only thing that would complain about it. It places an additional restriction on fid format.
We could have easily fixed it just by slightly changing our cite script as well. However I think that a check for oids is probably a worth while thing to do, and doesn't hurt anything. One issue with the fix that I realized however is, is that the check is a bit naive in that is just checks for an "oid" column. So if someone creates there own column named oid, things will probably go a miss. Do any of the postgres guru's know of a better way of looking up if a table has an oid in postgres? Perhaps by querying the system tables? -Justin Jody Garnett wrote: > Hi Andrea, seems we are into day number 2. >> Sorry, I thought the procedure was first release then try CITE but yes, >> now I think about it, it does not make sense... > No worries, have the time I give it a day and cite tests are not run > anyways. Lets just be sure Justin provided a test case showing what > the failure was rather then just a patch. >>> If we had not uploaded them the SF we could apply the patch and try >>> again ... as it is I do not think SF will let us replace >>> artifacts with exactly the same name :-( >> My bad... let's call it 2.2.2 or 2.2.1a? > Well I have not announced it yet, produce the 2.2.1 artifacts with the > patch, and we can rename the artifacts to say "geotools" rather then > "gt" if we have to. For now you can use your source forge admin access > to "hide" that release ... > > Jody > > !DSPAM:1004,452fc678138601425493344! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
