contacts.extensions

by Stefan Selariu » Wed, 29 Oct 2008 20:44:40 GMT


Sponsored Links
 Hi guys,
I'm trying to extend the contacts by adding additional fields to
contacts.people using contacts.extensions. My only problem is that have no
idea how to query the contacts.people using a join with contacts.extensions.
I'm not trying to modify/extend the contacts provider.

One very very ugly solution would be to query on contacts.extensions and
using the person ids to query the contacts.people (manual join) ... The idea
is to create an ListActivity which displays only the extended contacts.

I would like to be able to create a content provider that uses directly the
contacts.db (from the content provider) where i could use my join queries...
but from what I know this is not possible.

Do the content providers support joins? Or is there another way to create
this kind of joins?

One more thing... How can I use Contacts.People.Extensions?

Thanks

--~--~---------~--~----~------------~-------~--~----~



contacts.extensions

by Tughi » Thu, 30 Oct 2008 03:00:19 GMT


 Hi guys,
I'm trying to extend the contacts by adding additional fields to
contacts.people using contacts.extensions. My only problem is that
have no idea how to query the contacts.people using a join with
contacts.extensions. I'm not trying to modify/extend the contacts
provider.

One very very ugly solution would be to query on contacts.extensions
and using the person ids to query the contacts.people (manual
join) ... The idea is to create an ListActivity which displays only
the extended contacts.

I would like to be able to create a content provider that uses
directly the contacts.db (from the content provider) where i could use
my join queries... but from what I know this is not possible.

Do the content providers support joins? Or is there another way to
create this kind of joins?

One more thing... How can I use Contacts.People.Extensions?

Thanks
--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Why Gallery background complexity?

Just wondering why there is so much complexity involved in getting the
platform Gallery background.  The SDK provides a theme that contains
an attribute that is a drawable resource.   The theme is not a
drawable so it can't be used in a layout as a background.  The example
given is - 
http://developer.android.com/resources/tutorials/views/hello-gallery.html
- with these steps -

        TypedArray a =
obtainStyledAttributes(R.styleable.HelloGallery);
        mGalleryItemBackground = a.getResourceId(
 
R.styleable.HelloGallery_android_galleryItemBackground, 0);
        a.recycle();
        setBackgroundResource(mGalleryItemBackground);

where HelloGallery is a Them that includes the platform Theme
attribute that is the actual drawable  -

<resources>
    <declare-styleable name="HelloGallery">
        <attr name="android:galleryItemBackground" />
    </declare-styleable>
</resources>

All you really want is drawable/gallery_item_background.xml.
Unfortunately the very useful Gallery widget doesn't have default
focus behavior unless you do all this.

What is the benefit and/or rationale for all these layers?



-- 

2. [WTS] HTC Desire HD, HTC HD2 BNIB

Permisi, sebelum mudik, mau numpang jualan dulu..
Ready stock :
TC HD2 BNIB 2unit
TC Desire BNIB 20 unit

Semuanya Garansi resmi sistech singapore..

Bagi yg berminat, silahkan hubungi saya via japri mony...@gmail.com

Met natalan (bagi yg merayakan) 

€€€€.n ( o.. 
Sent from BlackBerry on 3

-- 
===============
"

3. Page Navigation Using button onclick in android

4. Apple's Solution. Was: Keystore

5. Camera zoom problem

6. [WTA] Bugs Galaxy S Froyo dan Ym Conference

7. Paging axis user.