On Thu, Jan 9, 2014 at 7:19 AM, Andrea Aime <[email protected]>wrote:
> On Wed, Jan 8, 2014 at 5:17 PM, Justin Deoliveira <
> [email protected]> wrote:
>
>>
>>
>>
>> On Wed, Jan 8, 2014 at 3:06 AM, Andrea Aime <[email protected]
>> > wrote:
>>
>>> On Thu, Dec 12, 2013 at 5:15 PM, Andrea Aime <
>>> [email protected]> wrote:
>>>
>>>> On Thu, Dec 12, 2013 at 5:11 PM, Paul Ramsey
>>>> <[email protected]>wrote:
>>>>
>>>>> Hi guys,
>>>>>
>>>>> You can spatialize your database any way you like, *but* we highly
>>>>> recommend using CREATE EXTENSION if the option is available to you. Check
>>>>> the pg_extensions_available table to see if the postgis extension is
>>>>> available in your database. The existence of template_postgis was always a
>>>>> packaging notion, and never a guaranteed thing by any stretch.
>>>>>
>>>>
>>>> In the case we're after a template database is not a strict
>>>> requirement, since it could be replaced by an eventually very long sql
>>>> script to run on creation
>>>> to setup the proper initial content of the database (so the field would
>>>> have to be a pointer to a file, no guarantees about any size limit of the
>>>> SQL in the script)
>>>> It just seems more complicated than just having a template database
>>>>
>>>
>>> Wondering if the following setup would be suitable for everybody:
>>> * create the database applying the CREATE_PARAMS optional parameter,
>>> that _might_ contain the indication to use a template
>>> * once the database is created, check if the postgis extension is
>>> already loaded by calling ..., if missing, check if the postgis extension
>>> is available and create it, if not, throw an exception (since the
>>> postgis extension is missing and cannot be added)
>>>
>>> Opinions? Clock is ticking, I'd like to add this before Jan 18th if at
>>> all possible
>>>
>>
>> Works for me. +1
>>
>
> Here is a pull request with the changes and a test:
> https://github.com/geotools/geotools/pull/341/files
>
> Looks good to me.
> I've chosen a hard to find in reality database name for the test... should
> we make it configurable
> in the postgis.properties file too?
>
Personally I think it is fine as is. If someone complains then perhaps we
can parameterize it.
>
> Cheers
> Andrea
>
> --
> == Our support, Your Success! Visit http://opensdi.geo-solutions.it for
> more information ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
--
*Justin Deoliveira*
Vice President, Engineering | Boundless
[email protected]
@j_deolive <https://twitter.com/j_deolive>
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
