Not NULL? Yes, always

[Former user]

Originally reported on Google Code with ID 33 ``` 1. Make flag "Not NULL" to be checked and disabled for change while setting primary key for new table.

As you can see, when I define field type as TEXT, attribute AUTOINCREMENT became disabled, because it does not make sense for it. So "complete sense" for primary key as well

2. Make flag "Not NULL" to be checked always by default. Usually, all fields are required to be defined for new record, and SOMETIMES it is not nessesary, and user can say "yes, this is not nessesary and I can omit it" ```

Reported by `owl.brainworker` on 2011-06-06 14:24:43

[Dane Iracleous]

``` I have to disagree with you on both issues.

1. A primary key CAN be a type TEXT. It is strange and not usually done, but it should not be prevented. On the other hand, it is impossible to have a field that is not an INTEGER to auto increment. The tool should allow anything that is possible under SQLite.

2. At least for me, most of my fields are TEXT types and do not need to be filled in. ```

Reported by `diracleo` on 2011-06-06 17:13:57 - Status changed: `Started`

[Former user]

``` It is strange but I agree with you for point 1, because what you said does not contradict my message at all. So read my message once again.

I said that flag "Not NULL" should be checked and disabled for change while setting primary key for new table. How does it contradict the fact that primary key can be text??? Of course, it can.

I am saying that flag "Not NULL" does not make sense for primary key, because it CAN NOT be null. So make it checked and disable it once flag "primary key" is checked. ```

Reported by `owl.brainworker` on 2011-06-06 19:43:57

[Dane Iracleous]

``` This is implemented in 1.8.7 now. ```

Reported by `diracleo` on 2011-06-07 04:37:49 - Status changed: `Fixed`