Would it be possible to create an actual VenueID relationship that is indexed, and unique?

I believe there will be more and more event 'info' driven from the venues.

Having a more 'programmatic' API for linking venues is key.

We are doing some custom integration with this and have considered the following:

Table : VenueSettings
ID
Name
Value
Category
ParentID
SortOrder


As such we can create venues with rooms of various sizes.
Depending on the 'size' of the room, the max attendees to the event will be set by the venue.

So venues would need to have an ID, and be NULL or an ID, as it's easy enough to create a venue on the fly w/ just a name.

Thoughts?

Brad

Brad,

I understand what you mean.

Currently in the Venue table, you can see there is a VenueID actually. The only thing is that the Events is linking to the Venues via Name. the idea was because we allow users to enter venues when creating a new event.

Maybe I will extend this idea, to allow users to have option to set: 1. Only choose from existing venues. 2. Allow enter venue as free text.

If you choose 1. in the settings, so there can be a relationship between Event and Venue.

Can you add two fields to the EventsCalendarVenue Table by default?

Lat
Lon

Also, this would be a great enhancement table to add to venues:

Venue Properties is a 'big list' format of hierarchical properties driven by the DNN PropertyDefinitionID
It can store extended values about a venue.

We have be using this extension in our projects, I thought I'd pass the datamodel along so that you could include it in your release, even if you don't implement it yet.

CREATE TABLE [dbo].[EventsCalendarVenueProperties](
[VenueId] [int] NOT NULL,
[PropertyDefinitionid] [int] NOT NULL,
[PropertyValue] [nvarchar](3750) NULL,
[PropertyCategory] [nvarchar](50) NULL,
[ParentID] [int] NULL,
[SortOrder] [tinyint] NULL,
[CreatedBy] [int] NOT NULL,
[CreatedDate] [datetime] NOT NULL,
[ModifiedBy] [int] NOT NULL,
[ModifiedDate] [datetime] NOT NULL,
CONSTRAINT [PK__EventsCalendarVe__66010E09] PRIMARY KEY CLUSTERED
(
[PropertyDefinitionid] ASC,
[VenueId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]

GO

Brad,

Thanks for the suggestion.

The fields are for: latitude and longitude?
Lat
Lon