Search found 181 matches
- 08 Dec 2021, 09:52
- Forum: Développement
- Topic: "error in your SQL syntax" en créant une base de données
- Replies: 11
- Views: 7651
"error in your SQL syntax" en créant une base de données
Bonjour Je crois que la priorité est de refaire marcher la distribution 1.5 , en réglant les deux bogues rencontrés lors de l'initialisation d'une base : le plantage en important des pays français. (enlever les 4 premières "Iles" fait disparaître le bug) le plantage, ensuite, en important ...
- 07 Dec 2021, 14:52
- Forum: Développement
- Topic: "error in your SQL syntax" en créant une base de données
- Replies: 11
- Views: 7651
Re: "error in your SQL syntax" en créant une base de données
Le problème de ce paramétrage de mysql est qu'il interdit l'utilisation du client mysql en ligne de commande: ~$ mysql -u root -p mysql: unknown variable 'sql_mode=NO_ENGINE_SUBSTITUTION' Pour ce problème, si le client et le serveur sont sur la même machine, il faut mettre la clause dans la section...
- 07 Dec 2021, 14:46
- Forum: Aide à l'utilisation
- Topic: SQL Error: Field 'Amount' doesn't have a default value
- Replies: 6
- Views: 4592
Re: SQL Error: Field 'Amount' doesn't have a default value
Il faut mettre la clause dans la section [server] et non [client-server] car ceci empêche de lancer un client sur la même machine que le serveur.
- 07 Dec 2021, 09:49
- Forum: Développement
- Topic: "error in your SQL syntax" en créant une base de données
- Replies: 11
- Views: 7651
Re: "error in your SQL syntax" en créant une base de données
Bonjour Vous êtes tombé sur un bug bloquant qu'on ne parvient pas à expliquer, seulement à contourner. Il se produit avec Gestinux 1.5.2 et aussi 1.6, sous Linux (Ubuntu, et donc maintenant aussi Slackware) avec MariaDb 10, mais je n'ai pas assez de retours sur les autres configurations, ce qui aide...
- 02 Nov 2021, 11:23
- Forum: Development
- Topic: Building process
- Replies: 1
- Views: 11523
Re: Strangeness in repository
Ok ! I never uploaded a 64 bits Windows because, up to Windows 10, the 32 bits version was running fine and quick enough on all recent Windows versions. Maybe this will change with the next Windows, I really don't know. Building for Linux on a Windows VM is interesting, but as I said for the reverse...
- 01 Nov 2021, 18:56
- Forum: Development
- Topic: import taxes
- Replies: 4
- Views: 4429
Re: import taxes
I do not fully understand why taxes' rates of 0% or negative are not allowed If you are sure that a 0% rate is useful, you can allow it in the entry. No drawback can occur, I think. About negative rate, I'm not so sure of the possible consequences. In my opinion, it must be allowed only after a rev...
- 01 Nov 2021, 18:32
- Forum: Development
- Topic: import taxes
- Replies: 4
- Views: 4429
Re: import taxes
The import system check if the rate exceeds xx% (some high value, I guess 100% but I did not check exactly); however it silently accepts any value below 0,01%, something which is not possible through the GUI Yes the rules are not the same as for keyboard input. But, in fact, importing taxes is not ...
- 01 Nov 2021, 18:24
- Forum: Development
- Topic: import taxes
- Replies: 4
- Views: 4429
Re: import taxes
If the "9" format is selected, the [Rate] field (which although it is an INTEGER, behaves as the Amount fields and is scaled by 100 in the database) is not scaled A "9" import format means simply that the decimal separator is ignored (when present), so the value is always rounde...
- 01 Nov 2021, 13:33
- Forum: Development
- Topic: Strangeness in repository
- Replies: 3
- Views: 5538
Re: Strangeness in repository
Hi About svn:eol-style property : The property svn:eol-style:native is advised to avoid errors during merge operations, in a number of sites But since I try to avoid merges with Delphi and Lazarus sources (for other reasons), I have never noticed any drawback when it is missing... If you want you ca...
- 27 Oct 2021, 20:13
- Forum: Development
- Topic: LogSql()
- Replies: 3
- Views: 4030
Re: LogSql()
Hi IMHO, the activation by a compilation directive is the good and usual way for such a thing. A log is needed only during developement, and only by some developer during a limited time and scope. So the $IFDEF looks well designed for that. It would not be good to activate it by a property of the co...