Skip to content
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.

charge_id column on charges table needs to be bigint #65

Closed
CamilleBB opened this issue Aug 9, 2018 · 2 comments
Closed

charge_id column on charges table needs to be bigint #65

CamilleBB opened this issue Aug 9, 2018 · 2 comments
Assignees
@gnikyt
Labels
bug Bug with the code
Milestone
v3.0.2

Comments

@CamilleBB
Copy link

Hi !
When I tried to activate the app on my store, I got a database error saying the value for "charge_id" column on "charges" table is over range (int range is -2147483648 to 2147483648 if I remember well).
My charge_id was something like 2917400000

I fixed it by setting (manually) the column as BIGINT.
@gnikyt gnikyt self-assigned this Aug 13, 2018
@gnikyt gnikyt added bug Bug with the code fix-in-progress In progress labels Aug 13, 2018
@gnikyt
Copy link
Owner

gnikyt commented Aug 13, 2018

Strange, I set this to be a bigint because I ran into issues as well when I created the feature... must've missed a commit :/ I'll patch in a fix for this, thanks!

@gnikyt gnikyt added this to the v3.0.2 milestone Aug 14, 2018
@paulcanning paulcanning mentioned this issue Aug 16, 2018
Closed
gnikyt added a commit that referenced this issue Aug 16, 2018
@gnikyt
Force fullpage_redirect views to use raw values, not escaped (issue #68…
142eab5 
… potential fix), use bigInt for charge IDs to fix issue #65
@gnikyt gnikyt added status-resolved and removed fix-in-progress In progress labels Aug 16, 2018
@gnikyt
Copy link
Owner

gnikyt commented Aug 16, 2018

Solved with v3.0.2 in a seperate migration to move int -> bigInt.

@gnikyt gnikyt closed this as completed Aug 16, 2018
@jimmy818 jimmy818 mentioned this issue May 7, 2020
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@gnikyt gnikyt

Labels
bug Bug with the code
Projects
None yet
Milestone
v3.0.2
Development

No branches or pull requests
2 participants
@gnikyt @CamilleBB