You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am new to using Phoenix, and have implemented it for some of our systems. We have a field called "updated_at" with a default field of "CURRENT_TIMESTAMP" and an "ON UPDATE" of "CURRENT_TIMESTAMP" aswell. I am getting an error "Setting 'update' is not allowed.".
I also struggled to find out what the option for this even was. I could not find any documentation around the different options that are available for fields. I did however see that this was following Phinx quite closely and assumed that those docs might work. I think if this is supposed to replace phinx, it either should have the docs of what options are supported, or support all of phinx's options and just have a link to their documentation so people don't get lost/confused to what the syntax is etc.
Appreciate any help
The text was updated successfully, but these errors were encountered:
Hi, thank you for your report. In time when Phoenix was created, I wanted to support only features that are common for both mysql and psql. As I personally don't use ON UPDATE event and also it is not supported by psql, it is not implemented. For now, you can use only plain query. Or if you want, you can implement it.
You are also right about documentation of column settings. We need to add this part.
Hi,
I am new to using Phoenix, and have implemented it for some of our systems. We have a field called "updated_at" with a default field of "CURRENT_TIMESTAMP" and an "ON UPDATE" of "CURRENT_TIMESTAMP" aswell. I am getting an error "Setting 'update' is not allowed.".
The code I used was this
I also struggled to find out what the option for this even was. I could not find any documentation around the different options that are available for fields. I did however see that this was following Phinx quite closely and assumed that those docs might work. I think if this is supposed to replace phinx, it either should have the docs of what options are supported, or support all of phinx's options and just have a link to their documentation so people don't get lost/confused to what the syntax is etc.
Appreciate any help
The text was updated successfully, but these errors were encountered: