On Sunday 25 June 2017 20:01:15 Paulo Lieuthier wrote:
> What's your opinion on the review requests already submitted? Please,
> tell me if there is anything to improve on them so we can get them
> merged.
The best would be to create your own branch in kopete git repository
(or in personal clone
On 22-06-2017 04:55, Pali Rohár wrote:
Adding another unique key just increase size of index and therefore any
operations with index would be slower.
Composed primary key (from id and subconversation_id) in Conversations
is mapped 1:1 to table Messages.
Therefore creating primary key just via "
On Thursday 22 June 2017 03:59:11 Paulo Lieuthier wrote:
> On 21-06-2017 11:45, Pali Rohár wrote:
> > On Tuesday 20 June 2017 08:38:01 Paulo Lieuthier wrote:
> >> On 20-06-2017 05:20, Pali Rohár wrote:
> >>> On Tuesday 20 June 2017 01:24:10 Paulo Lieuthier wrote:
> The new iteration:
>
>
On 21-06-2017 11:45, Pali Rohár wrote:
On Tuesday 20 June 2017 08:38:01 Paulo Lieuthier wrote:
On 20-06-2017 05:20, Pali Rohár wrote:
On Tuesday 20 June 2017 01:24:10 Paulo Lieuthier wrote:
The new iteration:
Conversations:
* id
* subconversation_id
* account
* type (1:1, group, channel)
* en
On Tuesday 20 June 2017 08:38:01 Paulo Lieuthier wrote:
> On 20-06-2017 05:20, Pali Rohár wrote:
> > On Tuesday 20 June 2017 01:24:10 Paulo Lieuthier wrote:
> >> The new iteration:
> >>
> >> Conversations:
> >> * id
> >> * subconversation_id
> >> * account
> >> * type (1:1, group, channel)
> >> * e
On 20-06-2017 05:20, Pali Rohár wrote:
> On Tuesday 20 June 2017 01:24:10 Paulo Lieuthier wrote:
>> The new iteration:
>>
>> Conversations:
>> * id
>> * subconversation_id
>> * account
>> * type (1:1, group, channel)
>> * entity_identifier (id of contact, group or channel)
>> * entity_display_name
On Tuesday 20 June 2017 01:24:10 Paulo Lieuthier wrote:
> The new iteration:
>
> Conversations:
> * id
> * subconversation_id
> * account
> * type (1:1, group, channel)
> * entity_identifier (id of contact, group or channel)
> * entity_display_name
>
> Messages:
> * id
> * conversation_id
> * sub
The new iteration:
Conversations:
* id
* subconversation_id
* account
* type (1:1, group, channel)
* entity_identifier (id of contact, group or channel)
* entity_display_name
Messages:
* id
* conversation_id
* subconversation_id
* timestamp
* sender_id (contact id, if available)
* sender_display_
On Sunday 11 June 2017 20:22:24 Pali Rohár wrote:
> On Sunday 11 June 2017 19:25:52 Paulo Lieuthier wrote:
> > > Plus there is missing something like "session" information. E.g. in
> > > jabber you can communicate with one person in more one-to-one
> > > chats. Every one is identified by jabber ros
On Sunday 11 June 2017 19:25:52 Paulo Lieuthier wrote:
> On 11-06-2017 08:28, Pali Rohár wrote> What does the "state" mean?
>
> Whether the message was really sent or failed to be sent.
Ok.
> > Also there is missing indication about direction. How to store
> > message which user of Kopete sent t
On 11-06-2017 08:28, Pali Rohár wrote> What does the "state" mean?
Whether the message was really sent or failed to be sent.
> Also there is missing indication about direction. How to store message
> which user of Kopete sent to IRC person? Or how to store message that
> was sent from user to
Hi!
On Sunday 11 June 2017 12:58:27 Paulo Lieuthier wrote:
> Hi all,
>
> So in this week I've been working on the schema. This is what I came
> up with:
>
> Conversations:
> * id
> * account
> * type (1:1, group, channel)
> * entity_identifier (id of contact, group or channel)
>
> Messages:
> *
Hi all,
So in this week I've been working on the schema. This is what I came up
with:
Conversations:
* id
* account
* type (1:1, group, channel)
* entity_identifier (id of contact, group or channel)
Messages:
* id
* conversation_id
* timestamp
* sender_id (contact id, if available)
* unknown_sen
13 matches
Mail list logo
