all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Orange
|
|
|||
|
|||
|
|
|
Uploaded Media/Content & Other Files
(7)
|
||||
| Media Name | File Type | Date | Description | |
| IMG_4356.JPG | Image/JPEG | 5/15/2017 | How cluster tables tie together. | |
| IMG_4357.JPG | Image/JPEG | 5/15/2017 | Current log in process | |
| adilas_database_tables.doc | Doc/Text | 5/12/2017 | ||
| full_database_copy.docx | Doc/Text | 5/12/2017 | ||
| Interactive map help file | Web/HTML | 2/22/2017 | This is a link to the help file for the interactive map. It shows the map and has a ton of other links to other images that we use for explaining where we are headed. It also explains the map a little bit and talks about some key points. | |
| full_database_copy.docx | Doc/Text | 2/22/2017 | This is a word doc that has a bunch of the steps listed out that we need to do to copy the full database. It started out as a small doc to list the steps but grew into a list of tables, what they contain, and what is needed per corp. This document is not finished yet, but a good start. | |
| adilas_database_tables.doc | Doc/Text | 2/22/2017 | This is a document that has all of the adilas database tables in it. The file is not done, but has a ton of info and is the start of a file that will define the whole database and what the different tables do and what the columns and/or fields are within each table. This is part of the database world building project. | |
|
Notes:
|
|
Alan came over to my house and we looked into the database world building project. This is where we will be splitting up databases and changing the underlying structure of what and how we store the data. We talked about a number of key things. Here is a small list as a reminder: - We started with some history and how in 2010, we started to map out the system. As we did that, we found that we were missing a huge date/time type component. - We lightly went over the interactive map graphic and the GPS core graphics and how they play in. Basically, as we get deeper, we are starting to see where things are going. - We talked about the current model and how the serves are setup with one shared database and one set of code. The new model will have a controller database and then smaller solar system (smaller groups of corporations). We still want the one-to-many relationship between one set of code and multiple databases. - We started talking about the ideal (a full and complete rewrite) vs. a smaller database only focus. Lots of good discussion there. We came up with some smaller barriers to the full and/or complete rewrite. They were: - >>> Time - time to finish, how long it will or could take. - >>> Framework (language) and technology to use. - >>> Talent and training for a project of this size. - >>> Multiple unknowns - scale, goals, funding, new and changing features. - >>> Multiple people that are doing the code. - >>> Lack of leadership/organization. - >>> API socket stuff (what we use and what they use). - >>> Everything ties to time. - We also covered some history on how we built and then broke model after model. We talked about how our current model has been built upon for the last 10+ years. We talked about how it is breaking in some places, fracturing in others, and general state of the platform. - We talked about going clear back to the login level to get things dialed in for the new database changes. This will tie into a corp key that starts the login process. We still need to buff this section out and get a better detailed plan. The concept is there, but the details are still kinda fuzzy. - Alan and I talked about database storage, optimization, and even I/O reads and writes and how to get better benefit out of the database models. We got kinda techy and even talked about changes, new indexes, and such. - Part of the discussion was talking about how adilas is somewhat of an add-on type product. We have a core or base and then add and virtually bolt on new features, changes, patches, etc. As we build and break things, we then start with what we have as the new core. It builds and builds as we go. - The last part of the conversation was dealing with existing code, pages, prep work, and where and how to find that. I will include a couple of word docs that we started (back a couple of years ago August/September of 2014). They are dealing with the database and what the different tables are and what the different fields do, hold, and how they interconnect. - One of our next goals is to get organized and look more into the cluster controller databases and what is needed. there. - As a side note, we talked about finishing up the first round using normal web code and then have Calvin translate that logic into his auto process (database to database) software tool. Here are some files that have been started as part of this project. - >>> top_secret/secure/master_corp_home.cfm - starting page for setting up the other cluster and solar system levels. - >>> top_secret/secure/create_new_cluster.cfm - create new cluster (domain or box level database - level 3) - >>> top_secret/secure/create_new_solar_system.cfm - create new solar system (database within a cluster - level 4) - >>> top_secret/secure/create_new_solar_system_part_2.cfm - migrate data from older shared database to new solar system database. - >>> There are also tons of cfc's that have been started to help with this process. They are top_secret/cfc/admin.cfc, admin_2, 3, 4, 5, A2B, C, D2I, J2O, P, Q2R, S, T, U2Z (all of these files have top_secret/cfc/admin_[whatever].cfc. |