I would create a new database, load that table in the new database, and
create a view from your database used by rails to the new db you created.
That way you will only be recreating the view and not the whole table.
If you are dealing with indexes on the table, be sure to add the indexes
before
Thanks for the swift reply!
So the application will utilize two databases, one just for the
zipcodes table? How would I go about that? Know of any decent
references for something like this?
On Nov 13, 1:50 pm, Darian Shimy dsh...@gmail.com wrote:
I would create a new database, load that
See if the following will help:
# Create two databases in the same server
create database zipcode;
create database rails;
# Create the zipcode table in the zipcode database
use zipcode;
create table zipdata...;
# Switch over to the rails app database and create the view
use rails;
create or
jrgoodner wrote:
Hey there, I'm not super familiar with MySQL, so please forgive me if
I say something stupid.
I have a large database table (it includes every zipcode in the U.S.,
along with its city,state,latitude,longitude), and it seems that we
are frequently
4 matches
Mail list logo
