Hi Michaël,
> Not sure this is the expected behaviour.
> Currently, It behaves like Run Datastore Query (it uses it).
> The OpenJUMP layer name is saved as is ("New") ,
> but it connects to the
> database
> with the right query (select * from "abc").
> I could change the layer name at the time it is saved to the database,
> but I'm not sure
> every user wants that.
Maybe a ToolTip would help to indentify the real tablename
of the database-layer
> FYI
> Currently, when creating a new table, the plugin tries to guess the
> geometry
> type (POINT, LINESTRING...) from the layer content.
> I think this is dangerous and I want to open it and use GEOMETRY type
> every time (now, thanks to the replace option,
> the user is free to create a
> table with more constraints if he needs to restrict data type).
> Any idea ?
>
I agree with you. It is a problem to guess the geometrytype
because POINTS, LINESTRINGS and POLYGONS ... can be on the same
layer.
The type GEOMETRY works with all "Layertypes" I think so.
But what happens when you open a PostGIS table with, maybe,
POLYGON type and save it back to PostGIS.
Do you want also change the type to GEOMETRY?
Regards
Uwe
Am 04.12.2012 22:06, schrieb Michaël Michaud:
> Hi Uwe, postgis users
>>
>> 1. If you save a layer to PostGIS with a table name with capital letters
>> ("ABC") and you save the project and open it again the layer is empty.
> Should be fixed with r3102
>> 2. If you save the layer "New" to PostGIS with a different tablename
>> than the layername with small letters ("abc") and you save the project
>> and reopen it you see the geometry but the layername is the old one
>> ("New") and not "abc".
> Not sure this is the expected behaviour.
> Currently, It behaves like Run Datastore Query (it uses it).
> The OpenJUMP layer name is saved as is ("New") , but it connects to the
> database
> with the right query (select * from "abc").
> I could change the layer name at the time it is saved to the database,
> but I'm not sure
> every user wants that.
>
>> 3. The tablenames in the ComboBox for the table are not in alphabetic
>> order.
> Should be alphabetical now (upper cases preceding lowercase, though)
>>
>> 4. The tablenames in the ComboBox for the table are appears twice or
>> thrice after testing with various names.
> Should be fixed.
>
> FYI
> Currently, when creating a new table, the plugin tries to guess the
> geometry
> type (POINT, LINESTRING...) from the layer content.
> I think this is dangerous and I want to open it and use GEOMETRY type
> every time (now, thanks to the replace option, the user is free to create a
> table with more constraints if he needs to restrict data type).
> Any idea ?
>
> Michaël
>>
>> 5. The "Replace all features from table" does not work
>> if the table does not exist. The old plugIn tested if the
>> table exist and create a new table if not.
>>
>> Regards
>>
>> Uwe
>>
>> Am 02.12.2012 19:10, schrieb Michaël Michaud:
>>> Hi Uwe, PostGIS users,
>>>
>>>> > I let 4 options in the PostGIS writer
>>>> > - create / overwrite : copy the entire layer content in the db
>>>> (remove the db table first if it exists)
>>>>
>>>> Please do not remove the table in the option "overwrite"
>>>> because you delete the constraints too.
>>>> Please use DELETE FROM tableName to delete all rows
>>>> but to keep the constraints.
>>> I added a 5th option to get this behaviour in the Save as PostGIS table
>>> plugin. Please test and report.
>>> (I used TRUNCATE instead of DELETE, let me know if there is any plus to
>>> use DELETE)
>>> to test it, use revision r2092 or more in
>>> https://sourceforge.net/projects/jump-pilot/files/OpenJUMP_snapshots/
>>>
>>> There has been much work on the PostGIS related plugins since version
>>> 1.4.
>>> It is still not complete and it is still difficult to work in a
>>> collaborative way on a single big database,
>>> but hopefully, the set of new capabilities is consistent enough for the
>>> upcoming OpenJUMP release.
>>>
>>> I added some information in the wiki :
>>> https://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Working_with_Databases
>>>
>>>
>>>
>>> From my point of view, the only missing features for OJ 1.6 is now
>>> tests and documentation ;-)
>>>
>>> Michaël
>>>
>>>
>>>>
>>>> Uwe
>>>>
>>>>
>>>> Am 20.11.2012 09:20, schrieb Michaël Michaud:
>>>>> Hi Uwe,
>>>>>> to insert rows to an existing table (with primary keys)
>>>>>> out of OpenJUMP can cause problems if the table is very large.
>>>>>> Maybe you have duplicated keys or the table is so large that
>>>>>> it costs too much time to insert rows into an existing table.
>>>>> I let 4 options in the PostGIS writer
>>>>> - create / overwrite : copy the entire layer content in the db (remove
>>>>> the db table first if it exists)
>>>>> - insert : insert all features from the layer into the table without
>>>>> using keys,
>>>>> and without removing existing record from the db
>>>>> - update : insert/update features using an identifier
>>>>> - update with delete : same as previous, but authorizing deletion
>>>>>
>>>>> I think what you want to do is the first option. Isn't it ?
>>>>>
>>>>> On the other hand, splitting very large tables to be able to update
>>>>> them is
>>>>> not always an option. OpenJUMP user is not supposed to be the database
>>>>> administrator. So ther option can be useful too.
>>>>>
>>>>> Michaël
>>>>>
>>>>> I prefer an other way:
>>>>>>
>>>>>> Loading the whole table to OpenJUMP.
>>>>>> *No* limit, maybe to 100000 rows, or so.
>>>>>> Why a limit? This can cause errors if the table has more than 100000
>>>>>> rows.
>>>>>> If the table is too large, the user has to split it.
>>>>>> Then you can edit the table with OJ and after that you can write the
>>>>>> whole layer back to the database
>>>>>> (with delete from tablename and then insert ...).
>>>>>> This is very quick!
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Uwe
>>>>>>
>>>>>>
>>>>>> Am 17.11.2012 19:17, schrieb Michaël Michaud:
>>>>>>> Hi Uwe, others,
>>>>>>>
>>>>>>> I'd like to have PostGIS users feedback about the following
>>>>>>> question :
>>>>>>> Save as PostGIS table can save a layer as a new PostGIS table
>>>>>>> or update an existing PostGIS table with different options.
>>>>>>>
>>>>>>> IMHO, only the first option (create new table) should set the
>>>>>>> postgis
>>>>>>> table as the new Datasource for the layer (and save it in the
>>>>>>> project).
>>>>>>>
>>>>>>> In other cases, the layer may contain only a few features and
>>>>>>> the table we connect to maybe a huge table. Setting this huge table
>>>>>>> as the new datasource may freeze the application.
>>>>>>>
>>>>>>> Any comment ?
>>>>>>>
>>>>>>> Michaël
>>>>>>>
>>>>>>>> Uwe, Landon,
>>>>>>>>
>>>>>>>> I had forgotten Uwe's mail, but I now have added a bug report
>>>>>>>> and will tackle it before 1.6 final release.
>>>>>>>>
>>>>>>>> Michaël
>>>>>>>>> Hi Landon,
>>>>>>>>>
>>>>>>>>> no, I got no response.
>>>>>>>>>
>>>>>>>>> I tested it now again with the latest nightbuild
>>>>>>>>> (Version 20121111 snapshot rev.3073), but I have the
>>>>>>>>> same problem.
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> Uwe
>>>>>>>>>
>>>>>>>>> Am 12.11.2012 17:26, schrieb Landon Blake:
>>>>>>>>>> Uwe:
>>>>>>>>>>
>>>>>>>>>> Did you ever get a response or a solution to this problem?
>>>>>>>>>>
>>>>>>>>>> Landon
>>>>>>>>>>
>>>>>>>>>> On Mon, Sep 24, 2012 at 12:00 AM, Uwe Dalluege
>>>>>>>>>> <uwe.dallu...@hcu-hamburg.de> wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I can not read projects with PostGIS layer.
>>>>>>>>>>> OJ Version 20120924 snapshot rev.3004
>>>>>>>>>>> OS: W7 (64 bit) and XP (32 bit).
>>>>>>>>>>>
>>>>>>>>>>> 1. Add A New Layer.
>>>>>>>>>>> 2. Draw a geometry.
>>>>>>>>>>> 3. Save the layer to PostGIS with Save Dataset As.
>>>>>>>>>>> 4. Save Project As...
>>>>>>>>>>>
>>>>>>>>>>> 5. When I open the project again the project is empty
>>>>>>>>>>> and the category System is deleted.
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>>
>>>>>>>>>>> Uwe
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Live Security Virtual Conference
>>>>>>>>>>> Exclusive live event will cover all the ways today's security
>>>>>>>>>>> and
>>>>>>>>>>> threat landscape has changed and how IT managers can respond.
>>>>>>>>>>> Discussions
>>>>>>>>>>> will include endpoint security, mobile security and the
>>>>>>>>>>> latest in
>>>>>>>>>>> malware
>>>>>>>>>>> threats.
>>>>>>>>>>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Jump-pilot-devel mailing list
>>>>>>>>>>> Jump-pilot-devel@lists.sourceforge.net
>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Monitor your physical, virtual and cloud infrastructure from a
>>>>>>>>> single
>>>>>>>>> web console. Get in-depth insight into apps, servers, databases,
>>>>>>>>> vmware,
>>>>>>>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>>>>>>>> Pricing starts from $795 for 25 servers or applications!
>>>>>>>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>>>>>>>> _______________________________________________
>>>>>>>>> Jump-pilot-devel mailing list
>>>>>>>>> Jump-pilot-devel@lists.sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Monitor your physical, virtual and cloud infrastructure from a
>>>>>>>> single
>>>>>>>> web console. Get in-depth insight into apps, servers, databases,
>>>>>>>> vmware,
>>>>>>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>>>>>>> Pricing starts from $795 for 25 servers or applications!
>>>>>>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>>>>>>> _______________________________________________
>>>>>>>> Jump-pilot-devel mailing list
>>>>>>>> Jump-pilot-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Monitor your physical, virtual and cloud infrastructure from a
>>>>>>> single
>>>>>>> web console. Get in-depth insight into apps, servers, databases,
>>>>>>> vmware,
>>>>>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>>>>>> Pricing starts from $795 for 25 servers or applications!
>>>>>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>>>>>> _______________________________________________
>>>>>>> Jump-pilot-devel mailing list
>>>>>>> Jump-pilot-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
