Thursday, June 9, 2011

Documentation updated

Originally I had got the semantics of the "Visit" class in the tutorial stupidly wrong. The language used by the guide is no extra attribute, it clearly has to be a part of the embedded ID.

How do I know? Well, in the original you couldn't insert two visits from the same ZIP area to the same city, but with different languages used by the guide. You always got an update of the same record, because the ID, combining only city and ZIP, was the same.

Now we have an association between three entities, City, Zip and Language, all three contributing their respective IDs to the embedded ID, and the "numberOfVisitors" has become a "totalNumberOfVisitors". Whenever new data about a visit comes in, we look if an instance of Visit already exists. If so, we increment its total number of visitors, otherwise we create a new object. Maybe I should even call the class not Visit but VisitStats or something like that.

I have not made a new release, but I have already updated the documentation, the tutorial as well as, the archive that also contains sample sources. You would have got it with the next release, but I figure it is bad style keeping nonsense on the web as soon as you recognize it's nonsense :)

1 comment:

  1. Just like in any popular industry with giant numbers of merchandise, you are better off starting with a selected niche associated to a long-tail keyword somewhat than an overly-generic search. This waterproof, rechargeable plug is Bluetooth and app appropriate, meaning long-distance couples have another way to liven up the separation. The toy has 4 manual vibration settings and extra obtainable on the app. It’s good for rhythm-lovers, with a Club Vibe mode that synchronizes motion to the noises around you. However, if you’ve ever traveled with a sex toy, might have|you could have|you may have} endured the marginally awkward expertise of TSA rifling by way of your bags—made even worse in case your toy starts rose sex toy vibrating.