Andrea Aime wrote: > Justin Deoliveira ha scritto: >>> Got it. So that will be fixed by 2.0.1? 2.1? I ask because it's not a >>> trivial change, once we enter RC stage it will be more risky to fix. >> Well, are there any open bugs that were are sure depend on this? The >> only issue I know of is not being able to change the table structure >> underneath a feature type. Any others? > > None that I know of. Yet for this use case it is a regression :-) > The use case by itself is not common for people publishing existing > data, might hit commonly people trying to setup an empty table > for WFS-T editing thought (since you probably iterate a few times > before getting the table structure right). >
Since this 'might' hit people trying to do something that I imagine may be fairly rare (as it's not something we've commonly done), I'd say we should wait for a bug report on it. At some point I'd love to have a nice REST API to set up a new table, and even to change the table structure, so people could make a new empty WFS-T table through GeoExt. If a user actually reports it then it should shoot to high priority. If we fix regressions on everything that could potentially be a problem we'll be in beta/rc land for a long time. > Cheers > Andrea > -- Chris Holmes OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
