Database Query Error

Error
Database query error


I just discovered this.  It's what people see after filling out the join form on my site, and pressing the submit button.

How nice.  It certainly explains why I haven't been able to get anyone to join my site lately.  Everything else throughout the entire site works except for the friggin join form.  Aw... who needs members anyway.  Red is a good color for a notice like this, because that's what I see frequently when working with Dolphin.

It sure would be nice to have a little bit more to go on than the cute little red notice above, but I don't.  Does anybody have any suggestions as to how I may go about tracing this error?  ...or perhaps someone could just put me out of my f*@king misery already.

Crap like this just makes me want to give up on this damn platform.

My opinions expressed on this site, in no way represent those of Boonex or Boonex employees.
Quote · 25 May 2010

Hi Houston Smile

Did you add a Height field using Predefined values in your join form ? Coz I saw the same too short error message when testing the join form of my site and that was due to quotes and/or double quotes in feet and inches values of height (like 4'6" - 5'2"). I changed these values with metric values (like 181 - 190cm)... that solved my problem.

Life is a fatal disease, sexually transmissible - Virginity is carcinogenic! Ask here for vaccine.
Quote · 25 May 2010

 

Error
Database query error


I just discovered this.  It's what people see after filling out the join form on my site, and pressing the submit button.

How nice.  It certainly explains why I haven't been able to get anyone to join my site lately.  Everything else throughout the entire site works except for the friggin join form.  Aw... who needs members anyway.  Red is a good color for a notice like this, because that's what I see frequently when working with Dolphin.

It sure would be nice to have a little bit more to go on than the cute little red notice above, but I don't.  Does anybody have any suggestions as to how I may go about tracing this error?  ...or perhaps someone could just put me out of my f*@king misery already.

Crap like this just makes me want to give up on this damn platform.

 

 

 

i had this to, i install the new d7.0.1 and updeta the DB from the old one and i get this error to and i see that i have missing NEW_ITEM i ues in the old one and i just deleted them from the Fields Builder

Quote · 25 May 2010

Also might helpful if you could post a few lines from the database error email you received. Should be able to somewhat get an idea of what went wrong.

Nothing to see here
Quote · 25 May 2010

You can see log via editing

\inc\classes\BxDolDb.php

define( 'DB_FULL_DEBUG_MODE', false );

change to

define( 'DB_FULL_DEBUG_MODE', true );

so you will see full debug log

Quote · 25 May 2010

OK.... Here's the problem.  The last member to join my site, was assigned a user ID of 4294967295, which is 2^32 the largest number the mysql auto increment counter can handle.  Therefore Everything the user did, their ID # of 4294967295 was associated with their action.  I was able to go database diving and correct this users ID to '30'.

How this happened, I have no idea.  The problem now, is that the auto increment counter for the ID field in the profiles table is now sitting at '4294967295'.  I verified this by successfully submitting the join form to create a test account, and I was assigned the ID of '4294967295'.  Once a user gets assigned this ID, no one else can join a site, because Mysql will try to assign the same ID number to anyone that attempts to join, thus producing the error.

I'll have to figure out how to reset this counter to where it should be.  If anyone wants to jump in an save me some time, I'd sure appreciate it.  I'm tired of looking like an ass every time I ask people to join my site, and they encounter something like this.  I don't know what caused this, but it sure as hell wasn't anything I did.

My opinions expressed on this site, in no way represent those of Boonex or Boonex employees.
Quote · 25 May 2010

HL,

i am going to look into resetting the counter on auto_increment. i will also look into what might have caused it to wig out.

OK.... Here's the problem.  The last member to join my site, was assigned a user ID of 4294967295, which is 2^32 the largest number the mysql auto increment counter can handle.  Therefore Everything the user did, their ID # of 4294967295 was associated with their action.  I was able to go database diving and correct this users ID to '30'.

How this happened, I have no idea.  The problem now, is that the auto increment counter for the ID field in the profiles table is now sitting at '4294967295'.  I verified this by successfully submitting the join form to create a test account, and I was assigned the ID of '4294967295'.  Once a user gets assigned this ID, no one else can join a site, because Mysql will try to assign the same ID number to anyone that attempts to join, thus producing the error.

I'll have to figure out how to reset this counter to where it should be.  If anyone wants to jump in an save me some time, I'd sure appreciate it.  I'm tired of looking like an ass every time I ask people to join my site, and they encounter something like this.  I don't know what caused this, but it sure as hell wasn't anything I did.

how to do this for those who are wondering. go to phpmyadmin select the table you want to work with, then click on the operations tab, and set the next number you want it to count to, as in HL's case, you would put 31, and hit go. so the next time it auto_increments, the next number shall follow behind in ascending fashion.

HL, not able to locate what wigged out as we have no binary logs for mysql.

Regards,

DosDawg

When a GIG is not enough --> Terabyte Dolphin Technical Support - Server Management and Support
Quote · 25 May 2010

HL,

please check to see if you get the correct auto_increment number now. please register a user and let me know.

Regards,

DosDawg

When a GIG is not enough --> Terabyte Dolphin Technical Support - Server Management and Support
Quote · 25 May 2010

THE DAWG RULES! 

Dawg, I definitely owe you a few beers when you come to town.  Maybe we can even slam a few tequila shots.

My opinions expressed on this site, in no way represent those of Boonex or Boonex employees.
Quote · 25 May 2010

Is the 'Profiles' table the only one that would have been affected by this case of Dolphin gone berserk?

My opinions expressed on this site, in no way represent those of Boonex or Boonex employees.
Quote · 25 May 2010

HL, i checked all of your other tables, they all look ok except for the ajax_chat_user i think it was. also there was some other apps dbase you have on there the userID started @ 10000, i have reset that to 1, and auto_increment =2

Is the 'Profiles' table the only one that would have been affected by this case of Dolphin gone berserk?

i cant tell you what caused it, i just searched through several other databases to see if the sql server was looking to give up the ghost, and there were no problems. the issue is isolated to the HL account.

Regards,

DosDawg

When a GIG is not enough --> Terabyte Dolphin Technical Support - Server Management and Support
Quote · 25 May 2010

That reminds me. I need to drop those ajax_chat tables.  I was experimenting with an alternative to the useless chatbox that comes with D7.

I've seen forum posts here in the past where 2^32 appeared in peoples Dolphin database.  I have never, ever, experienced a problem like this with non-Dolphin sites I have had for a long time.

My opinions expressed on this site, in no way represent those of Boonex or Boonex employees.
Quote · 25 May 2010
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.