How to store lists of options in a web application

where does sharepoint online store data
sharepoint online database
where is sharepoint online data stored
best free to-do list app
to do list website
best to-do list app for iphone
storing sharepoint list data in sql server
connect sharepoint online list to sql server table

We are currently designing a new database and I'm not sure how I want to store my lists of options.

For example, if you have a list of priorities:

1  High
2  Medium
3  Low

or type:

1 email
2 phone
3 text

How should I be storing these?

Historically I have placed them in a database table ( Option 1):

Priorities

id description
1  High
2  Medium
3  Low

The result of this, is that they become foreign keys in other tables.

An alternative (Option 2), is to store them in code, as a list of constants.

Pros and Cons
Option 1
  • Much easier to maintain, no need to push code. You just add maintenance pages to edit the tables.
  • Many more database hits, every time you want to retrieve the list.
Option 2
  • Less hits on the db.
  • If the list need to be modified, you need to change the code and then push the code.

Have I missed anything? What is common practise?

Cheers


I would decide based on following factors :

1. Number of available values :

If it's just a set of 2 or 3 predefined values like priorities High, Medium, Low.. I would prefer to have it in codebase as constants. Because it is highly unlikely any new option will be added like very low or very very low etc

If the values are predefined but large in numbers, like maybe skillsets of an employee.. I would definitely put it in a database table.

2 . Possibility of values changing :

If these values are changing frequently and you want to give control to user maybe via an admin panel to manage these values, definitely store those in database table.

3. The usage frequency :

If these values are core of your system so that it's used in almost all queries to filter the results, then you need to also account for the performance :

For example : Let's say entire project depends upon High, Medium, Low priorities. You need to filter almost every query using the priorities then :

Having Constants will have the priority stored in tasks table :

$tasks = Task::whereIn('priority', [high_constant, low_constant])->get();

Having a separate table priorities and having relationship will with tasks using priority_id foreign key have:

$task = Task::whereHas('priority', function($q){
    return $q->whereIn('priority_name', ['high', 'low']);
})->get();

Depending on number of data you have and frequent queries you do, you can check which is affecting performance. If the difference is very small, I would prefer constants with points 1 and 2 taken care of.

4. Extras like Getting the ID :

Let's say you have a page to create new task which has a dropdown of priorities.

If you have a separate table, you will have to get the ID of that priority from the priorities table to save it as a foreign key while saving task in tasks table. (Really not a huge deal though but good to mentioning)

If you have constant, you can save that value directly.

Each of it having pros and cons, I would make my choice mostly in point 1 and 2 above.

Also, if you are making constants, I would suggest to make a laravel facade with a n alias and then have constants defined in it. So you can use it something like through out your project

Priority::HIGH or Priority::LOW

Data storage options in SharePoint Online, Table 1. Sample app storage option, Used for. SharePoint list add-in web, Customer notes. SharePoint list host web, Support cases. Northwind� Take a look at System.Configuration namespace. The application settings its well suited for small values. If you want to store complex objects System.Configuration classes can help you a lot. You can define your own tags to use inside Web.Config or App.Config files. – Arturo Martinez Mar 21 '11 at 14:58


I usually do it with the database and foreign keys. You are already hitting the database for the information, with a simple you you can grab the right value's instead of the id's.

But if its just these 2 lists... I'm not sure, i try to not use hardcoded value's in my code to make easy changes without updating the production server.

Simplest way to store lists and dictionaries in config files, Most of the custom application settings are usually stored in in AppSettings configuration section. This section provides built in key/value pair data� Microsoft Lists is a Microsoft 365 app that helps you track information and organize your work. Lists are simple, smart, and flexible, so you can stay on top of what matters most to your team. Track issues, assets, routines, contacts, inventory and more using customizable views and smart rules and alerts to keep everyone in sync.


I would go with option 2:

You can put it in an array in a seperate file, outside your code, so it would be easier to manage, like:

types.php

<?php
return ['type' => ['email','phone','text']];

And require it where you need it:

require '/types.php';

Store the array in a variable like $options and use $options['type'] in your code.

Ofcourse you would need to push your code again. Other option would be caching it.

How to Use a DropDownList UI Component in Your Web App, A dropdown list lets users select one option from a list of options. The list appears when the user clicks on the element or triggers it another way. How To Restrict YouTube and Google Play Store on Android Devices /mobile phonesSteps to Restrict Google Play store and You tube /2020/07/how-to-restrict-youtube-and-google-play-store-on-android-devices-smart-phones.html


11 best to do list apps of 2020, We've done the research to bring you the very best options. We then tried the top-rated apps in every respective app store, and spent way too much time migrating Todoist (Windows, macOS, Android, iPhone, iPad, Web). Server-side options for storing page information typically have higher security than client-side options, but they can use more Web server resources, which can lead to scalability issues when the size of the information store is large. ASP.NET provides several options to implement server-side state management.


List Data Types, Within an application, a user filling out a New Patients form can select all the allergies that pertain to them from the provided options. There are three List data � On the Web Applications Management page, select a web application, and then in the General Settings group on the ribbon, click Outgoing E-mail. On the Web Application Outgoing E-Mail Settings page, in the Mail Settings section, type the name of the SMTP server for outgoing email (for example, mail.fabrikam.com) in the Outbound SMTP server box.


Forms in HTML documents, The BUTTON element; The SELECT , OPTGROUP , and OPTION elements before submitting the form to an agent for processing (e.g., to a Web server, to a mail server, etc.) Authors generally use this control type to store information between The default value for this attribute is "application/x-www-form- urlencoded". Introduction: Panoramio is an application that enables digital photographers to geo-locate, store and . organize their photographs-and to view those photographs in Google Earth and Google. Maps. This application where users can upload and geo-locate photos of the world, explore the world through other people's photos, and join a community of other