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

column names as numbers causes memory exhausted error #94

davidpede opened this Issue Sep 29, 2016 · 2 comments


None yet
3 participants
Copy link

davidpede commented Sep 29, 2016

Jason, as discussed in Slack. Using numbers as column names in a custom db table seemed to cause a loop which eventually exhausts memory. Looks like XPDO is treating them as non-strings. Adding a row to table $xpdo->newObject was the trigger in this case.

This is the loop:
(DEBUG @ C:\xampp\htdocs\repo\revolution\core\xpdo\xpdo.class.php : 1362)</h5><pre>Returning ancestry for myTableName: Array ( [0] => xPDOSimpleObject [1] => xPDOObject )

Which results in:
<b>Fatal error</b>: Allowed memory size of 134217728 bytes exhausted (tried to allocate 24 bytes) in <b>C:\xampp\htdocs\repo\revolution\core\xpdo\om\xpdoobject.class.php</b> on line <b>2390</b><br />


This comment has been minimized.

Copy link

wshawn commented Oct 3, 2016

This might be a legitimate bug, but I am sorely interested in why column names would be numbers? Doesn't that defeat the whole OOP thing?


This comment has been minimized.

Copy link

Jako commented Oct 3, 2016

It could be a database restriction:

Identifiers may begin with a digit but unless quoted may not consist solely of digits.

Maybe they are not quoted by xPDO for some reason …

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment