DB Schema Change....

[Jacob]

As part of our 5.0 release process, we are working through the schema and making some changes that will improve consistency.

Here are two of the current items. I wanted to give as much of a heads up as possible to the community.

1) Ensuring consistent boolean database types
· Changing existing ‘on’,’off’,’yes’,’no’ values to be stored as 0 or 1
· Changing the database column type to the appropriate type (no more varchar, enums)
· Changing vardefs.php files to reflect new schema changes

2) Resolving Date and Time column storage differences where they are related within the same module
· Merging time (hh:mm:ss) value with date column
· Removing time column
· Changing database column type for affected db types accordingly
· Changing vardefs.php files to reflect new schema changes


Jacob

[ruchida]

2) Resolving Date and Time column storage differences where they are related within the same module

Hi

This is a good change for a developer if it also means a custom field can support a date&time field.

[Jacob]

That is the plan.

[kpit]

One other thing I would like to see is the ability to choose between a drop down or multi-select on the same custom field. I would also like to have the concept of Custom Relationship that can be defined within the studio. this would allow for more extensive relationship creation between existing modules that may not be aware of a potential relationship especially in dealing with 3rd party modules.

[longreach]

Right now, building a multi-select field in the system, and maintaining the ability to report and filter on it - is not an easy job. Not sure what current plans may be on this front.

[Jacob]

I think that I did something similar a week or two ago (but I did it for the search view). I changed the application to have an additional search field that was a drop down, but I wanted it displayed as a multi-select field. This involved primarily changing the var-def definition of the element. Is this what you are looking for?