Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation update #153

Open
tranfuga25s opened this issue Jan 8, 2014 · 1 comment
Open

Documentation update #153

tranfuga25s opened this issue Jan 8, 2014 · 1 comment

Comments

@tranfuga25s
Copy link

On the Readme.md said:

ALTER TABLE users ADD facebook_id BIGINT(20) UNSIGNED NOT NULL

The problem is that when you update the schema to get into account the new field it will be converted to:
'facebook_id' => array('type' => 'integer', 'null' => false, 'default' => null, 'length' => 20)
but in a new creation of the schema will get the field to be INT(20)
This causes a problem with the autosave user feature that will create a new entry on the table, but the field of facebook_id will be cutted off.

Please change the documentation to float to let the schema reflect a bigger number in the field.
Sorry, I'm an spanish speeker

@tranfuga25s
Copy link
Author

Sorry, FLOAT doesn't work either...
So, please add a comment that after an schema create or schema update shoud change the field type to double or BIGINT(20).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant