Membership View - country column for second address
0 views
Skip to first unread message
Steve
Dec 11, 2009, 8:29:48 PM12/11/09
to LDSql
First off, thank you for the great product! It has made it much
easier for me to program the Android version of WardTools.
In the Membership View there are two sets of columns to store
addresses. In the second set, most of the columns are prefixed with
"2-" to distinguish it from the first set of address column names.
The country column in the second set of addresses is not prefixed so
it's name is identical to the column in the first set of address. Of
course columns in SQLite have to have unique names, so it renames it
from "Country" to "Country:1". Not a huge deal, but I wanted to bring
it to your attention as I assume it was intended to be called "2-
Country". For the purposes of my code, it really doesn't make a
difference what the name is, because I map the column names to
constant fields in my code (so if a column name gets changed, I only
need to change my mapping, rather than all the references of that
column name in my code).
easier for me to program the Android version of WardTools.
In the Membership View there are two sets of columns to store
addresses. In the second set, most of the columns are prefixed with
"2-" to distinguish it from the first set of address column names.
The country column in the second set of addresses is not prefixed so
it's name is identical to the column in the first set of address. Of
course columns in SQLite have to have unique names, so it renames it
from "Country" to "Country:1". Not a huge deal, but I wanted to bring
it to your attention as I assume it was intended to be called "2-
Country". For the purposes of my code, it really doesn't make a
difference what the name is, because I map the column names to
constant fields in my code (so if a column name gets changed, I only
need to change my mapping, rather than all the references of that
column name in my code).
boomerbubba
Dec 11, 2009, 9:04:32 PM12/11/09
to LDSql
Steve,
Thanks for the catch.
My bad. I will fix the name of this column in the next release to say
"2-Country"
As you may have figured out, my intent with the Membership view is to
replicate the original table layout from the MLS export file
Membership.csv, reconstructing that as a denormalized view. And "2-
Country" is what MLS calls this column.
I can't wait to try your Android app!
Thanks for the catch.
My bad. I will fix the name of this column in the next release to say
"2-Country"
As you may have figured out, my intent with the Membership view is to
replicate the original table layout from the MLS export file
Membership.csv, reconstructing that as a denormalized view. And "2-
Country" is what MLS calls this column.
I can't wait to try your Android app!
boomerbubba
Dec 11, 2009, 11:15:30 PM12/11/09
to LDSql
BTW, I think that abstracting the column names with your own meta
names is a good strategy for an application.
Within LDSql, I am trying to stay close to the conventions of the MLS
exports themselves, where applicable. And I rather expect those may
not be very stable in the near-to-intermediate future. There is a lot
of development going on in Salt Lake -- including a new geocoded
member table, a new web site application, a new HT/VT application and
possibly more integration of some of these elements with each other
and with MLS. I just hope that the export files basically remain
supported, but they obviously are the tail on the dog there.
MLS 3.1.2 was released today. AFAIK it does not affect the export
files, but I have not done a full regression test.
names is a good strategy for an application.
Within LDSql, I am trying to stay close to the conventions of the MLS
exports themselves, where applicable. And I rather expect those may
not be very stable in the near-to-intermediate future. There is a lot
of development going on in Salt Lake -- including a new geocoded
member table, a new web site application, a new HT/VT application and
possibly more integration of some of these elements with each other
and with MLS. I just hope that the export files basically remain
supported, but they obviously are the tail on the dog there.
MLS 3.1.2 was released today. AFAIK it does not affect the export
files, but I have not done a full regression test.
Reply all
Reply to author
Forward
0 new messages