Aaron J. Seigo said the following, On 2006-12-29 07:36: > ran into an oddness: integers are only allowed literal integer values for > default values. this is obviously a bit odd since it's perfectly valid in > most databases to use a procedure that returns an integer as the default > value. > > is this done this way so as to be "lowest common denominator" friendly or is > this just functionality that hasn't been implemented yet?
I've just double checked that (1.6 branch from SVN). Implemented since 1.1 alpha 1 (2006-08-09) and works for me - I especially put effort in serializing/deserializing QVariant constants exactly to be able to set default values of many types. The "default value" line edit in the property editor of the Table Designer, should accept any text values, so you can enter numbers and text. Boolean fields can even have set true/false/null default value using a special combobox. There is no support for functions yet, e.g. you cannot enter now() to get the current date as the default. -- regards / pozdrawiam, Jaroslaw Staniek Sponsored by OpenOffice Polska (http://www.openoffice.com.pl/en) to work on Kexi & KOffice: http://www.kexi-project.org, http://www.koffice.org KDE3 & KDE4 Libraries for MS Windows: http://kdelibs.com, http://www.kde.org _______________________________________________ Kexi mailing list [email protected] https://mail.kde.org/mailman/listinfo/kexi
