|
| "Null" Value in data base (MySql) |
| Iniciado por THEWORLDASGARP, 29,oct. 2018 10:15 - 2 respuestas |
| |
| | | |
|
| |
Miembro registrado
91 mensajes |
|
| Publicado el 29,octubre 2018 - 10:15 |
Hello,
Has anyone already worked on the "Null" problem?
When writing to a file a "Null" value, windev returns a 0 (zero).
So the database expects a" nul"l value, and a zero is sent, the database (in my case "MySql") causes program crash.
Thanks for your advices. |
| |
| |
| | | |
|
| | |
| |
Miembro registrado
20 mensajes |
|
| Publicado el 01,noviembre 2018 - 12:17 |
Yes. Tackled this just recently. To write NULL to MySql (rather than 0 or an empty string) use the following syntax.
Table.Item..NULL = True |
| |
| |
| | | |
|
| | |
| |
Miembro registrado
91 mensajes |
|
| Publicado el 05,noviembre 2018 - 11:28 |
Ok, thanks Stephen.
But my problem is more complex.
I explain:
ChnToto is a chain
ChnToto = Null
On debugging, we find that Windev has stored a "0" (zero) in "ChnToto".
I totally lose the initial information (=> <Null>).
How to force the compiler to keep this information without having to use the "Variant" type?
I feel that you have to go through a complex variable, or a class.
Thanks for the statement "Table.Item..Null = True / False".
I do not know. Is it valid for all bases? (SQLserver, DB2 / 400 ...)
Thanks for your advices. |
| |
| |
| | | |
|
| | | | |
| | |
|