It would indeed be great if we could use an arbitrary version of an object
to continue to build upon. Now, I have to start all over on each object that
was touched by somebody who didn't agree (yet) to the CTs, which is
annoying, as it disrupts the entire history.
Jo
2011/9/5 Ian Sergeant
>
> I
On 01.09.2011 08:19, Michael Kugelmann wrote:
On 31.08.2011 10:44, Nick Whitelegg wrote:
I would go so far as to say, don't delete *anything* until legally
you absolutely have to.
I would like to somehow modyfy this statement: we should replace the
data not delete it! So please remap the info
> > [@newer=2011-08-01]
> >restricts the data to only those data last edited after the given
> >date. This is only possible in combination with another conditional.
>
> Why wasn't something like [@timestamp>2011-08-01] used?
Well, at first, because there is no [@older=..] or [@timestamp<.
> [@newer=2011-08-01]
> restricts the data to only those data last edited after the given
> date. This is only possible in combination with another conditional.
Why wasn't something like [@timestamp>2011-08-01] used?
--
Darafei "Komяpa" Praliaskouski
OSM BY Team - http://openstreetmap.by/
Heya,
Same problem.
If you use \d command into psql you will see all tables have "postgres"
owner. You must assign them your user.
ALTER TABLE geometry_columns OWNER TO ;
ALTER TABLE nodes OWNER TO ;
ALTER TABLE relation_members OWNER TO ;
ALTER TABLE relations OWNER TO ;
ALTER TABLE schema_in
5 matches
Mail list logo
