Codeigniter oracle db driver

I have had this bug well, I think it is a bug anyways - I was wrong before, plenty of times for a while now, but was to lazy to even report it. I was just kinda working around it. The above setup works perfectly fine when running the app. However when I try to do migration here is where the problems start: php spark migrate results in the below:.

The workaround for this problem is to comment out the DSN part of the. When I do the above, the migrations run almost perfectly. Obviously, this kills the app itself, so once I am done with migration I need to un-comment the DSN line in order to have the app working.

Now, the reason I have written almost over there, is because this work fine the first time I run migration. However when I add new migration file I get the below:. Here's how my migration files look like:. So, why on earth is the CI trying to run the migration again for those that have clearly already been run? The text was updated successfully, but these errors were encountered:.

Not sure about the first part I would probably have to run some tests locally but about the second - you are using a different connection group. That's why CodeIgniter is trying to run all the migrations one more time - migrations history is unique per connection group. Sorry, something went wrong.

Ah, crap - sorry I've paste the wrong part of the code, probably because they are the same, this is still a playground, prod does not really means production in this case. I made some tests on the latest develop and I couldn't reproduce these connection errors. You may optionally store multiple sets of connection values. If, for example, you run multiple environments development, production, test, etc. Then, to globally tell the system to use that group you would set this variable located in the config file:.

It can be anything you want. You can also save your configuration values within a. The values should be name following this format, where default is the group name:. The database port number. To use this value you have to add a line to the database config array. The returned value depends on the underlying driver in use. Useful for checking how much rows were created, updated or deleted during the last executed query.

When strict mode is enabled, if you are running multiple groups of transactions and one group fails, all subsequent groups will be rolled back. If strict mode is disabled, each group is treated autonomously, meaning a failure of one group will not affect any others. Jump to Post. Facebook Like. Twitter Tweet. Be a part of the DaniWeb community. Sign Up — It's Free!

Reply to this Topic. This topic is old! No one has contributed to this discussion in over 3 years.