Re: [JPP-Devel] Default Type for bigint

2013-10-02 Thread Eric Lemesre
Hi Michaël Yes i always uses OpenJump. And I tried to do accept as GIS tools by my society (a big europeen insurance society). If I resume the situation: handle identifier( sequence) by integers is not sure ( I don't understand why, but I trust you ) but for others values is preferable because re

Re: [JPP-Devel] Default Type for bigint

2013-10-02 Thread Michaël Michaud
Hi Eric, Nice to see you still use OpenJUMP ;-) Currently, I'm not in favour of this change and have a few reasons : I'm working on a new postgis driver where I need to manage database identifiers. Often, database identifiers use bigint (from sequence). bigint are naturally converted to java l

[JPP-Devel] Default Type for bigint

2013-10-02 Thread Eric Lemesre
Hi, in com.vividsolutions.jump.datastore.jdbc.ValueConverterFactory Currently the bigint in database table is transcribed into a String object type. But the default type of aggregation is also bigint. for example: SELECT code_departement, count (*) as nb FROM anyTable GROUP BY 1 nb has bi

Re: [JPP-Devel] starter script

2013-10-02 Thread edgar . soldin
On 01.10.2013 22:09, Michaël Michaud wrote: > Hi Ede, > > A few days ago, I ran OpenJUMP on a windows server with 16G RAM, > and I noticed that it gave nearly 16G to the JVM (I first thought it gave > even more as it showed 17 000 000 000 bytes). > In the script you wrote : > use 100% of ram as de