Displaying 7 results from an estimated 7 matches for "address_typ".
Did you mean:
address_type
2012 Apr 05
0
Polymorphism, acts_as_relation gem and nested attributes
...on
def change
create_table :details, :as_relation_superclass => true do |t|
t.timestamps
end
end
end
class CreateEmails < ActiveRecord::Migration
def change
create_table :emails do |t|
t.string :address
t.string :address_type
t.string :detail_id
t.timestamps
end
end
end
class CreateUsers < ActiveRecord::Migration
def change
create_table :users do |t|
t.string :name
t.string :username
t.string :password
t.timestamps...
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
...el inlinees
// PROBE RECORDS
// A list of NPROBES entries. Each entry contains:
// INDEX (ULEB128)
// TYPE (uint4)
// 0 - block probe, 1 - indirect call, 2 - direct call
// ATTRIBUTE (uint3)
// 1 - internal linkage, 2 - dangling
// ADDRESS_TYPE (uint1)
// 0 - code address, 1 - address delta
// CODE_ADDRESS (uint64 or ULEB128)
// code address or address delta, depending on Flag
// INLINED FUNCTION RECORDS
// A list of NUM_INLINED_FUNCTIONS entries describing each of the inlined
// callees....
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