Downloads

The most recent releases, v 0.9.13.3 and v 0.9.12.3, are comprised of:

A SQLite script to create the raw MLS_Export_Ward database. This script is called Create_MLS_Export_Ward.sql.
A structurally created but unpopulated MLS_Export database file. (You can use this instead of the creation script.)
A SQLite script to create the LDSql_Ward database. This script is called Create_LDSql_Ward.sql
A created LDSql_Ward database file, structured but unpopulated except for several tables of strings, associated lookup codes, and U.S. postal abbreviations. (You can use this instead of the creation script.)
A SQLite script to populate the LDSql_Ward database from the MLS_Export_Ward raw database.

Version 0.9.13.3 and a corresponding v 0.9.12.3 change the loading logic to accommodate a recent bug in the MLS export files, which was causing some home and visiting teaching assignments to be missed. This is a workaround which, unfortunately, increases the rare probability of ambiguous member names in the home and visiting teaching tables (when two or more members have the same Preferred Name in MLS).

If the underlying bug in MLS is ever fixed, these versions of LDSql will be deprecated.

Version 0.9.13.1 and a corresponding v 0.9.12.1 fixed a bug in the date-handling logic that had affected age calculations in a small number of records. The date fix applies to both. Which version is right for particular implementers depends on how they choose to handle a recent change in the MLS exports.

The v 0.9.13.x release supports MLS version 3.3.0 and later, which dropped the MRN (Member Record Number) from the Membership.csv file.

LDSql itself is not forwards- or backwards-compatible with different versions of MLS exports. However, some implementers do maintain such compatibility in their loading processes. These implementers are best advised to use v 0.9.12.x of LDSql, which did support the MRN column directly. The MRN column in the final LDSql database is empty and deprecated, but still present to minimize damage to implementers' own programs.

The v 0.9.12 release added Spanish language support (credit due to Ryan McLaughlin and Steve Green). There also was a tweak to discard buggy MLS records in Organization.csv, and an attempt to optimize loading.

The v 0.9.11 release added functionality to deal with what seem to be errors found in some MLS export files -- duplicate spouse records for some families.

The v 0.9.10 release added functionality to deal with duplicate or missing heads of household records. There also are enhanced views to warn of other ambiguities in the MLS export files.

The v 0.9.9 release alters the schema and scripts to support the loading of tables with certain confidential fields suppressed. This is so auxiliary leaders can use LDSql, or applications based on LDSql, without being exposed to the confidential data.

The process is driven by the loading of the data upstream into the Membership table in the staging database MLS_Export_Ward, which is driven by the Membership.csv export file from MLS. Any of the following data columns can be globally suppressed from that MLS file by some external process:

   MRN
   Priesthood
   Married
   Mission
   Spouse Member
   Sealed to Spouse
   Sealed to Prior
   Baptized
   Confirmed
   Endowed
   Rec Exp

If LDSql detects that data for any of those columns is globally absent, it will gracefully treat all data derived from that confidential data as Nulls.

This release has been tested with output from MLS v 3.2.4.

The v 0.9.8 release updated the Primary view to conform to the Church's recent renaming of Primary classes. In addition, the columns that display each member's callings are enhanced to include the sustaining dates, and the columns that display home- and visiting-teaching assignments by member now include the companion's name. There also is a bug fix in the name of one column in the Membership view, and another to the triggers in the VisitingTeaching staging table to make the treatment of empty columns consistent.

(The v 0.9.7 release was lost due to versioning problems.)

The v 0.9.6 release primarily incorporated a change to make it compatible with MLS v 3.1.1. Althought the change was minor, this release is not compatible with earlier versions of MLS exports. Use an earlier version of LDSql for earlier versions of MLS.

The v 0.9.5 release is an extensive restructuring to accommodate similar restructuring introduced by MLS v 3.1.0.

These changes had the general effect of allowing the recording of phone numbers and email addresses for individual members as well as for households. Because of the limitations of MLS exports, this also affected the logic of how members and households are identified in the home- and visiting-teaching tables.

Almost all tables and views were affected, as were all the scripts. There were new, deleted and renamed columns for individual and household phone numbers and email addresses.

Because of the extensive restructuring, this version is not backwards-compatible with earlier versions of MLS. To load data from such earier MLS exports, use the LDSql schema and scripts from v 0.9.4.

Earlier Versions

The only change in v 0.9.4 was a reimplementation of three views as tables, which are populated at the time the LDSql_Ward database is loaded. This corrects performance deficiencies introduced with the new features of v 0.9.3.

The principal new features of v 0.9.3 were a view that emulates the New Member Report in MLS, as well as enumerated callings and home-and visiting-teaching assignments for each member, concatenated and formatted for display. (Some now-redundant columns were deprecated.) See the release notes in ReadMe.txt for details.

The principal new features of the prior release, v 0.9.2 were views that emulate the subreports of the Bishopric Action and Interview List in MLS, with extended fields also included: