Hi Claudius,

1) why you use viSQL so long? Valentina Studio should be much better

2) in Valentina Studio, you can modify tables in GUI, and it seems to me, in log of vstudio must be visible SQL commands which it executes.

Another way - open again Valentina Studio, make new diagram, add your table,
then start do your changes
- mark field index
- add NOT NULL

then exists command Apply Changes, and it also should show generated SQL command(s).

hmmmm sorry Ruslan....

I am old fashion and didn't know Valentina Studio. Thanks for help now it works. I have to learn using this handsome tool and not coder tool
I prefered SQL Commands but in future I will have an eye on Valentina Studio.

Half a year ago I was working already with V4RB 4.4.8 and Valentina Studio was much newer. So It was unable to open old stuff database without changing the database. So I decided to use viSQL because it was compiled with same version the database was created. Now I am up to date and it works fine for me.

thanks

Claudius

My point is that Valentina Studio self execute SQL commands,
so developer can learn a lots from it.

Diagram tool allow to developer DRAW changes, then generate SQL commands for that changes. This is cool

Actually you should repeat field definition:

ALTER TABLE EventName MODIFY EventArt VarChar(504) NOT NULL INDEXED