difference mySQL and Postgre

Classic Servoy
1

I have a strange difference in a Form linked to mySql-table / Postgre-table:

The Field is defined absolutely the same in:

  • in Postgre ( sys_tablviewflds ADD COLUMN flds_strg character varying(4096) is the same then in
  • the mySQL ( VARCHAR 4096)

But the appearance in the Form is not the same. On one hand I have a Dataprovider and in other Hand
I have no Dataprovider ( see Picture attachment)

[attachment=0]Prtscrn_01.jpg[/attachment]

Any Ideas, what I do wrong ?
Thank you for help

Prtscrn_01.jpg
Prtscrn_01.jpg1281×284 67 KB

2

At first glance I’d say that oFrm.controller.setDataProviderValue(…) is not correct, it should be forms.oFrm.controller.setDataProviderValue(…) if “oFrm” is the name of the form or forms[oFrm].controller.setDataProviderValue(…) if “oFrm” is a variable containing the form name.

3

ngervasi:
At first glance I’d say that oFrm.controller.setDataProviderValue(…) is not correct, it should be forms.oFrm.controller.setDataProviderValue(…) if “oFrm” is the name of the form or forms[oFrm].controller.setDataProviderValue(…) if “oFrm” is a variable containing the form name.

Nicola,
This is not possible the reason because:

  • oFrm values the pointer to the form itself: oFrm = forms[cFrmName]
  • the Postgre version is working fine, with the same form !

Any other suggestions ?
regards

4

what does it show in the ui?
do you there get a right value inside that column (especially if you make it none null)

Are you sure that the developer server definitions are in sync with the database?

5

jcompagner:
Are you sure that the developer server definitions are in sync with the database?

during making you a “perfect example that I did everything right”, I found the problem:

the fieldname (fld_strg insted of flds_strg) in mySql is wrong ! :oops: but I received not any errormessage.
MySql looks like:[attachment=1]Prtscrn_01.jpg[/attachment]

postgre looks like:[attachment=0]Prtscrn_02.jpg[/attachment]

Sorry Sorry for this stupid thing

Thank you all

Prtscrn_02.jpg
Prtscrn_02.jpg607×132 31 KB

Prtscrn_01.jpg
Prtscrn_01.jpg657×131 34.8 KB

6

stefanoni:
…the fieldname (fld_strg insted of flds_strg) in mySql is wrong ! :oops: but I received not any errormessage. …

Exactly, it would be nice if an error is thrown when assigning a value to a non-existing field of a foundset. The assignment does not have any effect whatsoever, so it’s wrong anyway.

7
I also see another typo. The name 'Postgre' does not exist. It's Postgres or PostgreSQL. The name Postgres comes from 'Post-Ingres' since it was the successor of Ingres.
8

michel:
Exactly, it would be nice if an error is thrown when assigning a value to a non-existing field of a foundset. The assignment does not have any effect whatsoever, so it’s wrong anyway.

Come to servoy world to see if maybe servoy 6 would take care of all this! ;)

9

ROCLASI:

I also see another typo.
The name ‘Postgre’ does not exist. It’s Postgres or PostgreSQL.
The name Postgres comes from ‘Post-Ingres’ since it was the successor of Ingres.

Funny ! Good to look behind sometimes… Thank you

P.S.
Then should be “PostgresSQL” to bee logic for me…

10

stefanoni:
Then should be “PostgresSQL” to bee logic for me…

True, but names are not always logical.

But here is a bit of history:
After the Ingres project Michael Stonebreaker started Postgres as the Post-Ingres project at Berkeley University.
Later in 1995, after Michael Stonebreaker left to Informix, the students of Berkeley replaced the POSTQUEL query language for SQL and renamed it Postgres95.
In 1996 the project departed from the University and started a new life as an Open Source project and to reflect the SQL support they named it PostgreSQL (pronounced as ‘Postgres-Queue-El’).
Nowadays the project is named PostgreSQL or Postgres for short (or Pg for even shorter).

Hope it makes more sense now ;)