Displaying 7 results from an estimated 7 matches for "address_types".
Did you mean:
address_type
2012 Apr 05
0
Polymorphism, acts_as_relation gem and nested attributes
I have the following polymorphic association set up with
acts_as_relation (https://github.com/hzamani/acts_as_relation)
Model code:
class Email < ActiveRecord::Base
belongs_to :detail
validates_presence_of :address
end
class Detail < ActiveRecord::Base
acts_as_superclass
has_many :emails
accepts_nested_attributes_for :emails, allow_destroy: true
2006 Apr 04
4
Aggregating two objects of the same type
I would like to have a customer that has references to two addresses,
a billing address and a shipping address. In a non-rails environment
I would have two keys in the customers table, billing_address_id and
shipping_address_id to reference the addresses. It appears that
ActiveRecord expects the parent id to reside in the child table,
regardless of whether the relationship is one-to-one or
2007 Jun 14
1
using 'socat' to relay Dovecot SASL's auth socket over TCP?
...different purposes. It might be one of the tools that one `has
already needed'."
which, iiuc (?), can bidirectionally bridge the Dovecot unix-socket to
a TCP socket that Exim can talk/listen to.
reading further, "address types"
(http://www.dest-unreach.org/socat/doc/socat.html#ADDRESS_TYPES) seem
to include BOTH unix & tcp sockets ...
can anyone here comment further on this?
known to work? possible? no way? etc etc
thanks!
2006 Apr 08
2
one-to-one relationship confusion
Hello,
I posted a similar email, earlier in the week, but I still must not be
getting it.
I have a customer that aggregates two addresses; a shipping address
and a billing address. Addresses can also be referenced by other
objects in a similar way, so I would really like to avoid putting the
keys referencing the customer or other objects in the addresses table.
Addresses are exclusively
2006 Jun 03
8
confused about ActiveRecord relationships
I am very confused about where to put the belongs_to and the has_one
(and other relationship identifiers). I have read the RDoc and the
agile book many times about this and I think i still see it backwards.
Let me outline my app so you have an understanding...
I have 2 tables:
Schools { id, school_name, address_id }
and
Addresses { street1, street2, city, state, zip, country }
*** this
2020 Aug 08
2
[RFC] Context-sensitive Sample PGO with Pseudo-Instrumentation
In addition to an IR block id or probe Id, we’ll also need to know the inline context of a probe if it comes from an inlinee. The current pseudo probe encoding is based on a DFS walk of the inline tree. A MIR BB may contain probes from different inlinees, and we may need to extend the BB-info format for encode the inline contexts there. I’m happy to work with you on a encoding format that can be
2020 Aug 08
3
[RFC] Context-sensitive Sample PGO with Pseudo-Instrumentation
Hi Rahman,
Thanks for sharing the BB-info section proposal which is a shiny idea. I think the BB-info and pseudo probes deal with a similar problem in different spaces, i.e., mapping hardware samples to corresponding basic blocks. In the context of pseudo probes, we much focus on mapping samples back to source-level blocks which is the input to the optimizer. Therefore we are building a