Re: GSoC History plugin

Joshua Joseph <[email protected]>
Newsgroups gmane.comp.kde.devel.kopete
Message-ID <CAKYNVbTRo48w3_77=N9PxCjdqbeAYGWxx7DUhPiYSxPY56D++A@mail.gmail.com>
On Thu, Jun 18, 2015 at 8:59 PM, Pali Rohár <[email protected]> wrote:

>
> >
> > I intended for the account field to be protocol
> > dependant, as you had said earlier, so that jabber can store full
> > JID.
> >
>
> But then you cannot show history! You will get Kopete::Acount::accountId
> and you cannot match anything in database against accountId if you store
> protocol dependent string into database... This is no go way.
>
> You will select Kopete::Contact object, from it you will ask for
> contactId() and this information you will use for searching for history
> messages in database. If you do not store contactId() into database how
> other you want to search for history which belongs to particular
> Kopete::Contact object?
>

I get it now.

We will have to store the contactId() also. I will need to get good column
names
to avoid confusion with the foreign key columns.



>
> --
> Pali Rohár
> [email protected]
>
> _______________________________________________
> kopete-devel mailing list
> [email protected]
> https://mail.kde.org/mailman/listinfo/kopete-devel
>
>


-- 
Thanks,
Joshua

_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.