Ruby on Rails

On Friday, November 1, 2019 at 12:12:18 AM UTC-4, Ariel Juodziukynas wrote:

If you have:

item has_many item_item_properties

item_item_property belongs_to item_property

then you can add a relationship on the item model

has_many :item_properties, through: :item_item_properties

Then you'll be able to call @item.item_properties to loop through the ItemProperty objects associated to that Item object.

Now, you say @item.item_item_properties.pluck(:item_property_id) returns an empty array, that's because the Item does not have associated properties and pluck does an SQL.

El vie., 1 nov. 2019 a las 0:52, fugee ohu (<fuge...@gmail.com>) escribió:

On Thursday, October 31, 2019 at 11:32:22 PM UTC-4, Ariel Juodziukynas wrote:

You can do @item.item_item_properties.each do |item_item_property| and handle that object inside the loop, I'm not sure why would you expect that item_item_properties relationship to return key, value pairs. I don't understand what you want to achieve, maybe you are trying to do it on the wrong path.

El vie., 1 nov. 2019 a las 0:27, fugee ohu (<fuge...@gmail.com>) escribió:

On Thursday, October 31, 2019 at 9:33:22 PM UTC-4, Ariel Juodziukynas wrote:

@item.item_item_properties returns a collection of objects, you are calling a method on something array-like, it makes no sense.

If you want to get all the item_property_ids you can do @item.item_item_properties.pluck(:item_property_id) for example. I'm not sure what you want to achieve.

El jue., 31 oct. 2019 a las 22:29, fugee ohu (<fuge...@gmail.com>) escribió:

On Thursday, October 31, 2019 at 2:15:48 PM UTC-4, Ariel Juodziukynas wrote:

Use `.size` instead of `.count`. "count" does a database query and since you only built the element the COUNT db query will return 0. "size" knows what to do if the association is already initialized so it will return "1" in your case (and if it's not already loaded it will run a COUNT db query).

El jue., 31 oct. 2019 a las 8:42, fugee ohu (<fuge...@gmail.com>) escribió:

> @item=Item.new

> @item.item_item_properties.build

> @item.item_item_properties.count
 => 0

Why doesn't my @item object have any item_item_properties after build method

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/161b90ed-b6b1-4d4d-9f67-fb70f0463621%40googlegroups.com.

How do I reference individual columns?

 2.3.3 :006 > @item.item_item_properties.item_property_id
NoMethodError: undefined method `item_property_id' for #<ItemItemProperty::ActiveRecord_Associations_CollectionProxy:0x0055d4167fd628>

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a80b3961-82df-4943-9e5a-adb764d516b7%40googlegroups.com.

Could I directly access key, value without pluck or otherwise like

 @item.item_item_properties.each do |key, value|

item_property_id

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/b2057f01-80e0-4816-8893-b783e30159f8%40googlegroups.com.

Display item_property attributes in form

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3a2c3dcf-3b21-49c9-8e49-9b2f276d7b6d%40googlegroups.com.

On Thursday, October 31, 2019 at 11:32:22 PM UTC-4, Ariel Juodziukynas wrote:

You can do @item.item_item_properties.each do |item_item_property| and handle that object inside the loop, I'm not sure why would you expect that item_item_properties relationship to return key, value pairs. I don't understand what you want to achieve, maybe you are trying to do it on the wrong path.

El vie., 1 nov. 2019 a las 0:27, fugee ohu (<fuge...@gmail.com>) escribió:

On Thursday, October 31, 2019 at 9:33:22 PM UTC-4, Ariel Juodziukynas wrote:

@item.item_item_properties returns a collection of objects, you are calling a method on something array-like, it makes no sense.

If you want to get all the item_property_ids you can do @item.item_item_properties.pluck(:item_property_id) for example. I'm not sure what you want to achieve.

El jue., 31 oct. 2019 a las 22:29, fugee ohu (<fuge...@gmail.com>) escribió:

On Thursday, October 31, 2019 at 2:15:48 PM UTC-4, Ariel Juodziukynas wrote:

Use `.size` instead of `.count`. "count" does a database query and since you only built the element the COUNT db query will return 0. "size" knows what to do if the association is already initialized so it will return "1" in your case (and if it's not already loaded it will run a COUNT db query).

El jue., 31 oct. 2019 a las 8:42, fugee ohu (<fuge...@gmail.com>) escribió:

> @item=Item.new

> @item.item_item_properties.build

> @item.item_item_properties.count
 => 0

Why doesn't my @item object have any item_item_properties after build method

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/161b90ed-b6b1-4d4d-9f67-fb70f0463621%40googlegroups.com.

How do I reference individual columns?

 2.3.3 :006 > @item.item_item_properties.item_property_id
NoMethodError: undefined method `item_property_id' for #<ItemItemProperty::ActiveRecord_Associations_CollectionProxy:0x0055d4167fd628>

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a80b3961-82df-4943-9e5a-adb764d516b7%40googlegroups.com.

Could I directly access key, value without pluck or otherwise like

 @item.item_item_properties.each do |key, value|

item_property_id

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/b2057f01-80e0-4816-8893-b783e30159f8%40googlegroups.com.

On Thursday, October 31, 2019 at 9:33:22 PM UTC-4, Ariel Juodziukynas wrote:

@item.item_item_properties returns a collection of objects, you are calling a method on something array-like, it makes no sense.

If you want to get all the item_property_ids you can do @item.item_item_properties.pluck(:item_property_id) for example. I'm not sure what you want to achieve.

El jue., 31 oct. 2019 a las 22:29, fugee ohu (<fuge...@gmail.com>) escribió:

On Thursday, October 31, 2019 at 2:15:48 PM UTC-4, Ariel Juodziukynas wrote:

Use `.size` instead of `.count`. "count" does a database query and since you only built the element the COUNT db query will return 0. "size" knows what to do if the association is already initialized so it will return "1" in your case (and if it's not already loaded it will run a COUNT db query).

El jue., 31 oct. 2019 a las 8:42, fugee ohu (<fuge...@gmail.com>) escribió:

> @item=Item.new

> @item.item_item_properties.build

> @item.item_item_properties.count
 => 0

Why doesn't my @item object have any item_item_properties after build method

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/161b90ed-b6b1-4d4d-9f67-fb70f0463621%40googlegroups.com.

How do I reference individual columns?

 2.3.3 :006 > @item.item_item_properties.item_property_id
NoMethodError: undefined method `item_property_id' for #<ItemItemProperty::ActiveRecord_Associations_CollectionProxy:0x0055d4167fd628>

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a80b3961-82df-4943-9e5a-adb764d516b7%40googlegroups.com.

You can do @item.item_item_properties.each do |item_item_property| and handle that object inside the loop, I'm not sure why would you expect that item_item_properties relationship to return key, value pairs. I don't understand what you want to achieve, maybe you are trying to do it on the wrong path.

On Thursday, October 31, 2019 at 9:33:22 PM UTC-4, Ariel Juodziukynas wrote:

@item.item_item_properties returns a collection of objects, you are calling a method on something array-like, it makes no sense.

If you want to get all the item_property_ids you can do @item.item_item_properties.pluck(:item_property_id) for example. I'm not sure what you want to achieve.

El jue., 31 oct. 2019 a las 22:29, fugee ohu (<fuge...@gmail.com>) escribió:

On Thursday, October 31, 2019 at 2:15:48 PM UTC-4, Ariel Juodziukynas wrote:

Use `.size` instead of `.count`. "count" does a database query and since you only built the element the COUNT db query will return 0. "size" knows what to do if the association is already initialized so it will return "1" in your case (and if it's not already loaded it will run a COUNT db query).

El jue., 31 oct. 2019 a las 8:42, fugee ohu (<fuge...@gmail.com>) escribió:

> @item=Item.new

> @item.item_item_properties.build

> @item.item_item_properties.count
 => 0

Why doesn't my @item object have any item_item_properties after build method

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/161b90ed-b6b1-4d4d-9f67-fb70f0463621%40googlegroups.com.

How do I reference individual columns?

 2.3.3 :006 > @item.item_item_properties.item_property_id
NoMethodError: undefined method `item_property_id' for #<ItemItemProperty::ActiveRecord_Associations_CollectionProxy:0x0055d4167fd628>

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a80b3961-82df-4943-9e5a-adb764d516b7%40googlegroups.com.

@item.item_item_properties returns a collection of objects, you are calling a method on something array-like, it makes no sense.

On Thursday, October 31, 2019 at 2:15:48 PM UTC-4, Ariel Juodziukynas wrote:

Use `.size` instead of `.count`. "count" does a database query and since you only built the element the COUNT db query will return 0. "size" knows what to do if the association is already initialized so it will return "1" in your case (and if it's not already loaded it will run a COUNT db query).

El jue., 31 oct. 2019 a las 8:42, fugee ohu (<fuge...@gmail.com>) escribió:

> @item=Item.new

> @item.item_item_properties.build

> @item.item_item_properties.count
 => 0

Why doesn't my @item object have any item_item_properties after build method

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/161b90ed-b6b1-4d4d-9f67-fb70f0463621%40googlegroups.com.

On Thursday, October 31, 2019 at 2:15:48 PM UTC-4, Ariel Juodziukynas wrote:

Use `.size` instead of `.count`. "count" does a database query and since you only built the element the COUNT db query will return 0. "size" knows what to do if the association is already initialized so it will return "1" in your case (and if it's not already loaded it will run a COUNT db query).

El jue., 31 oct. 2019 a las 8:42, fugee ohu (<fuge...@gmail.com>) escribió:

> @item=Item.new

> @item.item_item_properties.build

> @item.item_item_properties.count
 => 0

Why doesn't my @item object have any item_item_properties after build method

--
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 rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/161b90ed-b6b1-4d4d-9f67-fb70f0463621%40googlegroups.com.

Use `.size` instead of `.count`. "count" does a database query and since you only built the element the COUNT db query will return 0. "size" knows what to do if the association is already initialized so it will return "1" in your case (and if it's not already loaded it will run a COUNT db query).

On simplecov - tried to do "gem install simplecov" from that docker shell of yours?

On Thursday, October 31, 2019 at 6:13:23 AM UTC-5, walt wrote:

IMHO ".., I use just one Docker container" is the first order of (your) business to get straighten out :)

Using containers with Rails is quite a feast - and an added bonus is that once set up you have next to zero footprint on your 'own' computer (that is a blatant lye 'cause your code base needs to sit somewhere, and the docker images has to be in place too - but even that could be 'clouded')

Docker containers doesn't really start to shining until you let them ;)

That is - delegate delegate delegate - or: one container per "task" 

You'll have at least three containers spinning - again IMHO. An app container with the Puma webserver serving the Rails stuff, a database container for the Rails models to persist their data, and a container for a reversed NgINX proxy serving clients on 80/443 and forwarding the necessary requests to the 'animal' (Puma). Other container candidates are: Redis, Sidekiq, and memcached. Here are the observations by Cloud66 - https://blog.cloud66.com/containers-for-rails-developers-use-containers-while-staying-true-to-your-ror-roots/

Use hub.docker.com to load the necessary images, then use github.com to load the codebase, then 

docker-compose build

docker-compose up (-d if you'd like it to sit in the background=daemonized)

That's it - more or less

Getting there will take you through one/two hoops I know for sure but it's worth the journey!

Start by following this example: https://www.chrisblunt.com/ruby-on-rails-running-tests-with-guard-and-docker/ 

Chris Blunt did an excellent demonstration job!

Using containers with Rails is quite a feast - and an added bonus is that once set up you have next to zero footprint on your 'own' computer (that is a blatant lye 'cause your code base needs to sit somewhere, and the docker images has to be in place too - but even that could be 'clouded')

Docker containers doesn't really start to shining until you let them ;)

That is - delegate delegate delegate - or: one container per "task" 

You'll have at least three containers spinning - again IMHO. An app container with the Puma webserver serving the Rails stuff, a database container for the Rails models to persist their data, and a container for a reversed NgINX proxy serving clients on 80/443 and forwarding the necessary requests to the 'animal' (Puma). Other container candidates are: Redis, Sidekiq, and memcached. Here are the observations by Cloud66 - https://blog.cloud66.com/containers-for-rails-developers-use-containers-while-staying-true-to-your-ror-roots/

Use hub.docker.com to load the necessary images, then use github.com to load the codebase, then 

docker-compose build

docker-compose up (-d if you'd like it to sit in the background=daemonized)

That's it - more or less

Getting there will take you through one/two hoops I know for sure but it's worth the journey!

Start by following this example: https://www.chrisblunt.com/ruby-on-rails-running-tests-with-guard-and-docker/ 

Chris Blunt did an excellent demonstration job!

Cheers,

Walther

Yes.  However, I use just one Docker container that contains everything I need, including Ruby, Rails, Node.js, PostgreSQL, Redis, etc.  I know that my way is crude, but it works.  I can't move on to the docker-compose way of doing things until I figure out all the issues that are stopping me.

On Wednesday, October 30, 2019 at 11:07:06 AM UTC-5, Brandon McClelland wrote:

You said "When I log into my custom Docker container, I basically follow the same procedure that the people who rely on their host environments do." Can you run the tests successfully that way?

I thought that would work, but simplecov isn't loading.


On Wednesday, October 30, 2019 at 10:53:06 AM UTC-5, Brandon McClelland wrote:

You would do something like this (found at https://blog.codeship.com/testing-rails-application-docker/ after googling "running rails test with docker-compose run"):

docker-compose run -e "RAILS_ENV=test" app rake test

What's the full command for running the test suite?  Sadly, but this isn't a CS class that one can BS through with partial credit.

On Wednesday, October 30, 2019 at 7:25:06 AM UTC-5, San Ji wrote:

docker-compose run?

https://docs.docker.com/compose/reference/run/

I've contributed to the Octobox app (https://github.com/octobox/octobox).  I've been using a weird system of using Docker.  Instead of using it the normal way, I create my own custom Docker image for each Rails project that I'm on.  When I log into my custom Docker container, I basically follow the same procedure that the people who rely on their host environments do.

I'm trying to learn the more conventional way of using Docker with docker-compose, but I'm having difficulty finding out how you're supposed to run the test suite.

I've followed the instructions at https://github.com/octobox/octobox/blob/master/docs/INSTALLATION.md#using-docker-and-docker-compose .  While I've been able to get the development environment working, I have not been able to figure out how I'm supposed to run the test suite with the docker-compose command.  Exactly what is the command for running the test suite?