#72: database improvments
------------------------+---------------------------------------------------
Reporter: smoku | Owner: smoku
Type: enhancement | Status: new
Priority: minor | Component: storage
Version: 2.2 | Keywords:
------------------------+---------------------------------------------------
> From kolargol 2005-01-31 17:27
I can think of a few problems with the current database schema. For one
the
use of dashes (-) in field
names requires strange quoting. As far as I know this isn't portable
between
databases though I
haven't looked into it too deeply. Some of the field names aren't too
obvious,
i.e. collection-owner
should possibly be something like jid. I'm not sure what to think of the
way
some things are spanned
across tables when they probably don't need to be (i.e. active and
logout),
perhaps there is a reason I
haven't thought of.
It'd be nice to keep a record of when users logged in as well since if
you're
trying to work out when an
account was last active, going by logout time, you won't catch accounts
that
are currently logged in. In
addition you could use both login/logout times as a crude way of telling
which
users are currently
online. Perhaps another nifty feature would be to keep track of the last
IP
address that a user logged in
with.
----
current sql driver don't support UPDATE statment. in the future it would
be
good
to change the way that jd2 is handling sql queries. for now it act like
that:
when you edit for example roster - server sends DELETE to clear entry in
db-backend and then inserts all line into db - again - that is waste of
resource
and sql time, it is clear that it is better to use UPDATE statment for
that
type
of operations.
as this is not major performance "injury" this can be done as low priority
;)
--
Ticket URL: <http://jabberd2.xiaoka.com/ticket/72>
jabberd2 <http://jabberd2.xiaoka.com/>
jabberd2 project
_______________________________________________
jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
