Skip to content

Change Log

Ben Ambrose edited this page Sep 16, 2024 · 3 revisions

Always synchronize the SCM applications to the database version being used!

See the BuildMeAClub Wiki for info on matching-up the correct SCM application with the right SCM database. WIKI: Version Info.


SCM database - V1.1.5.3

This version introduces Teamed Events. Additional attributes (IsArchived, CreatedOn) for tables ContactNum and House. Special attribute EnableSimpleDisqualification (ON), EnableMemberShipStr (OFF) in table SwimClub. Table MembershipType renamed to SwimmerClass and schema change. Now child of SwimClub. (Let you sort entrants, for heats, on classification type.) The MSSQL SwimClubMeet database model is assigned the version 1.1.5.3 in the SCMSystem table.

SCM database - V1.1.5.2

Scheduling for events, club logos, additional house attributes, modified object permissions, FINA's disqualification codes and improved relationship names. The MSSQL SwimClubMeet database model is assigned the version 1.1.5.2 in the SCMSystem table.

SCM database - V1.1.5.1

This version fixed a few issues that 'I got wrong'🤔. Minor fixes. Mostly to do with 'BITS' assigned to 'ALLOW NULLS'. Plus some scalar functions were optimized. The MSSQL SwimClubMeet database model is assigned the version 1.1.5.1 in the SCMSystem table.

SCM database - V1.1.5.0

This was the first official GitHub release of the SwimClubMeet database. The SCM project had already been running a local swimming clubs for over two years. The MSSQL SwimClubMeet database model is assigned the version 1.1.5.0 in the SCMSystem table.

SCM database - V1.0.0.0

When I first wrote the application and gave it to my local swimming club the app didn't have a version number. As time went by, more clubs and schools asked if they could use the application. At this point I was handling the updating of each version with individual update scripts. V1.0.0.0 is the apps birth.


Changes in each BuildMeAClub release