Context Navigation

Changes between Version 3 and Version 4 of Ticket #3888, comment 2

v3	v4
53	53
54	54
55		6. The other nice thing about ~~this~~, is going this way, it's much easier to fix in 3.0 when PostgreSQL extension machinery will be improved and it doesn't break backward compatibility now. What you are asking for to me should really be done 3.0 if we think it's necessary.
	55	6. The other nice thing about encoding in the version, is going this way, it's much easier to fix in 3.0 when PostgreSQL extension machinery will be improved and it doesn't break backward compatibility now. What you are asking for to me should really be done 3.0 if we think it's necessary.
56	56
57	57	To solve the immediate need of having extension without-raster, as I have said time and time again, the easiest way (that doesn't break backward-compatibility) is to encode it in the extension version.