On Wednesday 17 June 2015 15:11:22 Joshua Joseph wrote:
> > And for handling problem with jabber resource now I got this idea:
> >
> > What about storing this?
> > * protocol
> > * account
> > * contact
> > * from_id
> > * to_id
> > * from_name
> > * to_name
> >
> > (from|to)_id will be full protcol *dependent* identifier, so jabber can
> > store full JID "user@host/resource" and account can represent your
> > local_id and contact your remote_id.
> >
> > But do not know now... Any idea? Make sense? At least it could be needed
> > to modify it to work with multi user group chat correctly...
> >
>
>
> Yes this makes sense.
>
This could probably work for normal 1 vs 1 chat. For group chat it needs
fixing... or not ("contact" column as string identifier of group
chat/room)? Or maybe using separate table?? Come up with something...
Anyway, proper SQL schema with good documentation is required.
(And maybe invent better column name for from_id/to_id... if you want to
use _id suffix only for foreign keys)
--
Pali Rohár
[email protected]
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
