I see a problem just now while moving to postgres
In the GenerateUuid.java line 131: updateStatement.setInt(2, ids.getInt(1));
on that table fails. This is because the column is a varbinary column and
not an int. In postgres the global_property tables is created as:
property character varying(255) NOT NULL DEFAULT ''::character
varying,
Thus, the setInt fails because its not an int column. All other tables have
primary key column as int and doesn't seem to be a problem... but for this
table it's causing problem.
Should I fix this by saying if(tableName.equals("global_property") then
setString??
Or should we add a int primary key column??
There are some places which recommend int primary key columns, but
global_property isn't going to be large table, and hence the question.
---
Regards,
Saptarshi PURKAYASTHA
My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE
On 22 July 2011 04:09, Darius Jazayeri <[email protected]> wrote:
> That sounds correct.
>
> -Darius
>
> PS- Burke, Ben, WTF is up with changing global_property.property to
> varbinary to make global property names case-sensitive? (
> https://tickets.openmrs.org/browse/TRUNK-94) I've been wondering why
> global_property.property shows up oddly in mysql workbench. 15 months later
> I'd like to say that I disagree.
>
>
_________________________________________
To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
[email protected] with "SIGNOFF openmrs-devel-l" in the body (not
the subject) of your e-mail.
[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
