[DiscordArchive] Want to return to the subject above, would be good 1st to check relations between tables since I add
[DiscordArchive] Want to return to the subject above, would be good 1st to check relations between tables since I add
Archived author: Zerocool • Posted: 2023-12-19T15:37:14.382000+00:00
Original source
Want to return to the subject above, would be good 1st to check relations between tables since I add my table and before I mve to anything else ?
Archived author: Abillister • Posted: 2023-12-19T15:38:28.619000+00:00
Original source
The tables don't really have hard relationships. Adding a table isn't going to inheriently break anything or modify anything.
Archived author: Abillister • Posted: 2023-12-19T15:40:05.093000+00:00
Original source
The code uses the tables as data dump locations and references it when needed. So until you write code that uses the table, it won't do anything.
Archived author: Zerocool • Posted: 2023-12-19T15:55:56.423000+00:00
Original source
Right, then by that you mean by filling data on my table, then lookup how I can make him 'parent' of the other 2 tables. Where I can check when the tables are called ? As I said, not so savvy with SQL
Archived author: Abillister • Posted: 2023-12-19T16:33:44.615000+00:00
Original source
None of that is handled in SQL. All if it is in the core code. So you would need to look in the code to see where those tables are currently called from, and then figure out how to "reorganize" that within the code. SQL is entirely working as a data repository, there are no true relationships in it.
Essentially imagine that everything is just stored in individual DBC or XML files. Then centralize those files into a "SQL" tables. That is all that is happening. It isn't being used as a "relationship database" it is just being used as a table structure of XML/DBC data - which each table representing a file. And even then only for "some" data...other data is entirely in the DBC files still.
Archived author: Abillister • Posted: 2023-12-19T16:34:35.608000+00:00
Original source
So you don't need to know/understand SQL relationships. You need to figure out what the code is doing and how you would implement a new structure using a XML/DBC to store your data...but instead of using that file put the data into a table in SQL.
Archived author: Abillister • Posted: 2023-12-19T16:36:39.967000+00:00
Original source
(I personally prefer to build all of my logic into SQL and I use the relationships as the basis of the logic, then just send the result of a query to the code page. But I've found I'm in the minority there - many developers/development use SQL as data storage with few to no hard relationships. The code contains all of that logic, and often times that logic will 'break' the relationships of the data within SQL [without the code to interpert it]).
Archived author: Zerocool • Posted: 2023-12-19T16:52:04.016000+00:00
Original source
I see what you mean. Pretty much had that thought of how the SQL acts in the EMU, since I wasn't sure exactly how the core behaved exactly. So, have to find where those tables are called and start build from there. The new table is already crated with some data stored at the moment.
Archived author: Zerocool • Posted: 2023-12-19T16:52:23.895000+00:00
Original source
Thanks for the info by the way, was helpful
Archived author: Abillister • Posted: 2023-12-19T16:56:00.148000+00:00
Original source
Sure. I would offer more insight but my code knowledge is bad [both in experience with AC and in general, I struggle with MVC]. So the best I can do is gesture towards the code base and grunt.