On Mar 14, 2013 1:58 AM, "avinash behera" <[email protected]> wrote: > > So, my requirement is :- > > I have an Image table & a related_image table. > image has_many related_images. > & related_images belongs to many images. > Those images in both the tables are in sequence(we can change the sequence- That will be a problem in case of belongs to many images). > > So, this seems to be a better option to save images as id. > In s3, I am saving both the images(images & related_images) in one folder as <id>.png or <id>.jpg > > After saving into s3, there are some other process to do like creating .plist file from the json objects & others. Here I require those data from s3. > > I was getting an interesting issue with heroku. > I was doing a db:reset & set the default id to start with 1000 & 10000 respectively. > It was working for the first time. If I do again a db:reset it goes. It starts from 1. > > I fixed it by adding migration file with :- > def change > execute "SELECT setval('images_id_seq', 1000)" > end > def change > execute "SELECT setval('related_images_id_seq', 10000)" > end > > & on console by :- heroku pg:reset DATABASE --confirm MY_APP_NAME > > So, now every time I reset, I need to run the migration & it works. > > > On Wed, Mar 13, 2013 at 2:16 AM, tamouse mailing lists < [email protected]> wrote: >> >> On Tue, Mar 12, 2013 at 7:58 AM, avinash behera >> <[email protected]> wrote: >> > The main reason I am doing this is :- >> > I am uploading some images to s3 amazon. >> > I am saving those images in s3 through rake script. >> > I have two tables having images. >> > Both are saving in one folder in s3. >> >> Do you mean they are being saved to the same bucket? Or do you mean a >> path under the bucket? S3 has it's own very unique method of storage. >> But you can easily store things in the same bucket, but specify a >> path-like prefix: >> >> s3://mybucket/table1/image-n.jpg >> s3://mybucket/table2/image-n.jpg >> >> table1 and table2 aren't really folders in S3, but they're good enough >> emulation to consider that for most uses. >> >> > I want to save those based on ids, so that there will not be any conflict. >> >> As stated, don't rely on the record ID in your database. Create a >> unique id for each image if you'd like, and use that to tag it, if >> that's how you want to go. >> >> -- >> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. >> To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. >> To post to this group, send email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > > > -- > Thanks, > Avinash > > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > >
Are images also capable of being related images? And vice versa? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
