dennis-fedco Posted March 14, 2014 Share Posted March 14, 2014 I am refactoring a huge legacy codebase. This codebase has SQL code everywhere. i.e. if any function needs some data from a database, it just calls the SQL right there and uses it.If I started from scratch I'd consider using Doctrine, or maybe some kind of an active record. But ... I basically want to refactor, and I am kind of lost ... What can I do with the SQL DB calls to refactor the code to a better more maintainable state? I mean what is the best practice today when it comes to using Databases in your code? Link to comment https://forums.phpfreaks.com/topic/286973-where-to-place-db-calls-during-refactoring/ Share on other sites More sharing options...
micah1701 Posted March 17, 2014 Share Posted March 17, 2014 Using an ORM is definitely the way to go, centralizing the codebase for making queries helps with future expansion (as well as if you need to swap out db technologies) and, with well implemented libraries, will help mitigate security holes such as sql-injection. For lightweight use, I'm a big fan of Idiorm (and Paris if you need active record support) http://j4mie.github.io/idiormandparis/ Link to comment https://forums.phpfreaks.com/topic/286973-where-to-place-db-calls-during-refactoring/#findComment-1472920 Share on other sites More sharing options...
gristoi Posted March 18, 2014 Share Posted March 18, 2014 you could follow the mvc pattern, or have a look at how symfony 2 deals with it by using repositories. Link to comment https://forums.phpfreaks.com/topic/286973-where-to-place-db-calls-during-refactoring/#findComment-1472970 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.