A better design would look like this: CREATE TABLE numbers ( minus_four_billions_two_hundred_ninety_four_millions_nine_hundred_sixty_seven_thousands_

A better design would look like this: CREATE TABLE numbers ( minus_four_billions_two_hundred_ninety_four_millions_nine_hundred_sixty_seven_thousands_two_hundred_ninety_six_is_even BOOLEAN, ... zero_is_even BOOLEAN, one_is_even BOOLEAN, two_is_even BOOLEAN, ... four_billions_two_hundred_ninety_four_millions_nine_hundred_sixty_seven_thousands_two_hundred_ninety_six_is_even BOOLEAN ) That design can store multiple versions of the data, making it more resilient to future changes in the even/odd property of numbers.