Tag Info

Having contextual models extend MY_Model which extends CI_Model has really practical benefits and this is exactly how my largest CodeIgniter application is designed (it wasn't a decision that I ...

It's a bit cumbersome to try to shoehorn JSON accessing syntax into a WHERE clause building method because the ->> fools with CodeIgniter's parsing of the expression. Ultimately, to keep using ...

Your Model: Because your method returns potentially multiple posts, your method name should use plural grammar - getPosts. The select() method has just two parameters. select($select = '*', $escape = ...

The "entirely" query builder version of your raw SQL is: public function getPrevNextRow(int $id): ?object { return $this->db ->select([ sprintf( ...

CodeIgniter's query builder can support what you need. Prepare the date range boundaries in PHP and the summing query will perform well. I never recommend using false as a fallback return value from a ...

$this->input->post('address') will return the array of numerically keyed rows. Simply loop over that payload and write your model method calls inside of that loop. Controller: $rows = $this->...

You are calling $this->db->get_compiled_select() as a what seems to be a debugging step. That method will return the build query as a string and then reset the query builder cache. To prevent ...

Your query involves only one table, so there is not need to qualify the table of origin when you mention columns. select('*') can be safely omitted because that is default behavior of a SELECT query ...

My CodeIgniter 3.1.13 project does not have a method called field_list(), but it does have field_data() which returns an array of objects with the following properties: name, type, max_length, default....

First problem is in your backend code that you are directly using the SELECT * statement query and accessing the data as item.data but there is no .data from back-end. So you can modify your ...