Migration changed :first row of table

i added a column to the model and then deleted it. after that a :first
call gave me a total arbitrary record. it changed from #9 to #75. all
the data still remains in the table

but a second migration to add the col with a loop to enter data gave
me an out of range integer error.

anyway to fix this? has anyone experienced this?

i can still out put the table with a sort, but i am concerned of the
integrity of the table.

some code would probably be handy - examples of what you’re trying.

Julian.

Learn Ruby on Rails! Check out the FREE VIDS (for a limited time)
VIDEO #3 out NOW!
http://sensei.zenunit.com/

Most database engines don’t guarantee the order of a result set unless
an ORDER BY clause is used. As I modify rows in PostgreSQL, the same
query returns the rows in different order unless I specify and ORDER BY.

Peace,
Phillip

Thanks, Phillip I too am using PostgreSQL the integer error was not
related.

On Apr 9, 7:12 pm, Phillip K. [email protected]

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs