2010-07-20 05:52:31 +00:00
< ? php
2014-06-30 20:16:21 +00:00
/**
* @ file mod / ping . php
*
*/
2010-07-20 05:52:31 +00:00
2012-07-13 14:09:29 +00:00
require_once ( 'include/bbcode.php' );
2012-10-27 11:43:39 +00:00
require_once ( 'include/notify.php' );
2012-05-22 23:01:07 +00:00
2014-06-30 20:16:21 +00:00
/**
* @ brief do several updates when pinged .
*
* This function does several tasks . Whenever called it checks for new messages ,
* introductions , notifications , etc . and returns a json with the results .
*
* @ param App & $a
* @ result JSON
*/
2014-07-01 00:03:00 +00:00
2012-07-13 14:09:29 +00:00
function ping_init ( & $a ) {
2011-09-28 07:30:22 +00:00
2012-07-13 14:09:29 +00:00
$result = array ();
$notifs = array ();
2012-05-22 23:01:07 +00:00
2012-07-16 04:06:07 +00:00
$result [ 'notify' ] = 0 ;
$result [ 'home' ] = 0 ;
$result [ 'network' ] = 0 ;
$result [ 'intros' ] = 0 ;
$result [ 'mail' ] = 0 ;
$result [ 'register' ] = 0 ;
2012-07-29 00:21:42 +00:00
$result [ 'events' ] = 0 ;
2012-07-29 00:39:26 +00:00
$result [ 'events_today' ] = 0 ;
2012-08-17 06:11:24 +00:00
$result [ 'birthdays' ] = 0 ;
$result [ 'birthdays_today' ] = 0 ;
2012-08-27 06:05:00 +00:00
$result [ 'all_events' ] = 0 ;
$result [ 'all_events_today' ] = 0 ;
2012-07-16 04:06:07 +00:00
$result [ 'notice' ] = array ();
$result [ 'info' ] = array ();
2012-07-26 05:55:43 +00:00
$t0 = dba_timer ();
2012-07-16 04:06:07 +00:00
2012-07-13 14:09:29 +00:00
header ( " content-type: application/json " );
2012-05-22 23:01:07 +00:00
2014-11-04 23:24:24 +00:00
$vnotify = false ;
if ( local_user ()) {
$vnotify = get_pconfig ( local_user (), 'system' , 'vnotify' );
$evdays = intval ( get_pconfig ( local_user (), 'system' , 'evdays' ));
}
// if unset show all visual notification types
if ( $vnotify === false )
$vnotify = ( - 1 );
if ( $evdays < 1 )
$evdays = 3 ;
2014-07-01 00:03:00 +00:00
/**
* If you have several windows open to this site and switch to a different channel
* in one of them , the others may get into a confused state showing you a page or options
* on that page which were only valid under the old identity . You session has changed .
* Therefore we send a notification of this fact back to the browser where it is picked up
* in javascript and which reloads the page it is on so that it is valid under the context
* of the now current channel .
*/
2014-02-22 21:33:18 +00:00
$result [ 'invalid' ] = (( intval ( $_GET [ 'uid' ])) && ( intval ( $_GET [ 'uid' ]) != local_user ()) ? 1 : 0 );
2012-07-16 04:06:07 +00:00
2014-07-01 00:03:00 +00:00
/**
* Send all system messages ( alerts ) to the browser .
* Some are marked as informational and some represent
* errors or serious notifications . These typically
* will popup on the current page ( no matter what page it is )
*/
2014-06-30 20:16:21 +00:00
if ( x ( $_SESSION , 'sysmsg' )){
2012-07-16 04:06:07 +00:00
foreach ( $_SESSION [ 'sysmsg' ] as $m ){
$result [ 'notice' ][] = array ( 'message' => $m );
}
unset ( $_SESSION [ 'sysmsg' ]);
}
2014-06-30 20:16:21 +00:00
if ( x ( $_SESSION , 'sysmsg_info' )){
2012-07-16 04:06:07 +00:00
foreach ( $_SESSION [ 'sysmsg_info' ] as $m ){
$result [ 'info' ][] = array ( 'message' => $m );
}
unset ( $_SESSION [ 'sysmsg_info' ]);
}
2014-11-04 23:24:24 +00:00
if ( ! ( $vnotify & VNOTIFY_INFO ))
$result [ 'info' ] = array ();
if ( ! ( $vnotify & VNOTIFY_ALERT ))
$result [ 'notice' ] = array ();
2012-07-16 04:06:07 +00:00
2014-02-07 05:31:42 +00:00
if ( $a -> install ) {
echo json_encode ( $result );
killme ();
}
2014-07-01 00:03:00 +00:00
/**
* Update chat presence indication ( if applicable )
*/
2014-01-28 23:52:54 +00:00
if ( get_observer_hash () && ( ! $result [ 'invalid' ])) {
2014-01-31 03:01:03 +00:00
$r = q ( " select cp_id, cp_room from chatpresence where cp_xchan = '%s' and cp_client = '%s' and cp_room = 0 limit 1 " ,
2014-01-29 10:25:21 +00:00
dbesc ( get_observer_hash ()),
dbesc ( $_SERVER [ 'REMOTE_ADDR' ])
2014-01-28 23:52:54 +00:00
);
2014-01-29 10:25:21 +00:00
$basic_presence = false ;
2014-01-28 23:52:54 +00:00
if ( $r ) {
2014-01-31 03:01:03 +00:00
$basic_presence = true ;
PostgreSQL support initial commit
There were 11 main types of changes:
- UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but
it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just
copied from Friendica. All of these instances, the LIMIT 1 was simply removed.
- Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit
integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice
to boot). Proper explicit boolean conversions were added. New queries should use proper conventions.
- MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_
func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There
were no true toggles (XOR). New queries should refrain from using XOR when not necessary.
- There are several fields which the schema has marked as NOT NULL, but the inserts don't specify
them. The reason this works is because mysql totally ignores the constraint and adds an empty text
default automatically. Again, non-compliant, obviously. In these cases a default of empty text was
added.
- Several statements rely on a non-standard MySQL feature
(http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten
to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run
a zillion times faster, even on MySQL.
- A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG,
UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_
- INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes
around the value -- assist functions added in the dba_
- NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such
thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are
handled in Zot/item packets automagically by quoting all dates with dbescdate().
- char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the
code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works
better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype
for all text fields in the postgres schema. varchar was used in a couple of places where it actually
seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code
actually validates data, new bugs might come out from under the rug.
- postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted.
bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function
was added to handle this transparently.
- postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax.
Statements were updated to be standard.
These changes require corresponding changes in the coding standards. Please review those before
adding any code going forward.
Still on my TODO list:
- remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting
- Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
q ( " update chatpresence set cp_last = '%s' where cp_id = %d " ,
2014-01-31 03:01:03 +00:00
dbesc ( datetime_convert ()),
intval ( $r [ 0 ][ 'cp_id' ])
);
2014-01-28 23:52:54 +00:00
}
2014-01-29 10:25:21 +00:00
if ( ! $basic_presence ) {
2014-01-28 23:52:54 +00:00
q ( " insert into chatpresence ( cp_xchan, cp_last, cp_status, cp_client)
values ( '%s' , '%s' , '%s' , '%s' ) " ,
dbesc ( get_observer_hash ()),
dbesc ( datetime_convert ()),
dbesc ( 'online' ),
dbesc ( $_SERVER [ 'REMOTE_ADDR' ])
);
}
}
2014-07-01 00:03:00 +00:00
/**
* Chatpresence continued ... if somebody hasn 't pinged recently, they' ve most likely left the page
* and shouldn ' t count as online anymore . We allow an expection for bots .
*/
PostgreSQL support initial commit
There were 11 main types of changes:
- UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but
it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just
copied from Friendica. All of these instances, the LIMIT 1 was simply removed.
- Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit
integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice
to boot). Proper explicit boolean conversions were added. New queries should use proper conventions.
- MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_
func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There
were no true toggles (XOR). New queries should refrain from using XOR when not necessary.
- There are several fields which the schema has marked as NOT NULL, but the inserts don't specify
them. The reason this works is because mysql totally ignores the constraint and adds an empty text
default automatically. Again, non-compliant, obviously. In these cases a default of empty text was
added.
- Several statements rely on a non-standard MySQL feature
(http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten
to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run
a zillion times faster, even on MySQL.
- A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG,
UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_
- INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes
around the value -- assist functions added in the dba_
- NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such
thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are
handled in Zot/item packets automagically by quoting all dates with dbescdate().
- char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the
code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works
better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype
for all text fields in the postgres schema. varchar was used in a couple of places where it actually
seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code
actually validates data, new bugs might come out from under the rug.
- postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted.
bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function
was added to handle this transparently.
- postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax.
Statements were updated to be standard.
These changes require corresponding changes in the coding standards. Please review those before
adding any code going forward.
Still on my TODO list:
- remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting
- Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
q ( " delete from chatpresence where cp_last < %s - INTERVAL %s and cp_client != 'auto' " ,
db_utcnow (), db_quoteinterval ( '3 MINUTE' )
);
2014-01-28 23:52:54 +00:00
2012-07-16 04:06:07 +00:00
if (( ! local_user ()) || ( $result [ 'invalid' ])) {
2012-07-13 14:09:29 +00:00
echo json_encode ( $result );
killme ();
}
2012-02-24 00:50:29 +00:00
2014-07-01 00:03:00 +00:00
/**
* Everything following is only permitted under the context of a locally authenticated site member .
*/
/**
* Handle " mark all xyz notifications read " requests .
*/
2014-06-30 20:16:21 +00:00
// mark all items read
if ( x ( $_REQUEST , 'markRead' ) && local_user ()) {
2013-02-04 03:07:01 +00:00
switch ( $_REQUEST [ 'markRead' ]) {
case 'network' :
2014-11-17 23:18:06 +00:00
$r = q ( " update item set item_flags = ( item_flags & ~%d ) where (item_flags & %d) > 0 and uid = %d " ,
2013-02-04 03:07:01 +00:00
intval ( ITEM_UNSEEN ),
intval ( ITEM_UNSEEN ),
intval ( local_user ())
);
break ;
case 'home' :
2014-11-17 23:18:06 +00:00
$r = q ( " update item set item_flags = ( item_flags & ~%d ) where (item_flags & %d) > 0 and (item_flags & %d) > 0 and uid = %d " ,
2013-02-04 03:07:01 +00:00
intval ( ITEM_UNSEEN ),
intval ( ITEM_UNSEEN ),
intval ( ITEM_WALL ),
intval ( local_user ())
);
break ;
case 'messages' :
2014-11-17 23:18:06 +00:00
$r = q ( " update mail set mail_flags = ( mail_flags | %d ) where channel_id = %d and not (mail_flags & %d) > 0 " ,
2013-02-04 03:07:01 +00:00
intval ( MAIL_SEEN ),
intval ( local_user ()),
intval ( MAIL_SEEN )
);
break ;
case 'all_events' :
2014-11-17 23:18:06 +00:00
$r = q ( " update event set ignore = 1 where ignore = 0 and uid = %d " ,
2013-02-04 03:07:01 +00:00
intval ( local_user ())
);
break ;
case 'notify' :
$r = q ( " update notify set seen = 1 where uid = %d " ,
intval ( local_user ())
);
break ;
default :
break ;
}
}
2014-11-17 23:18:06 +00:00
if ( x ( $_REQUEST , 'markItemRead' ) && local_user ()) {
$r = q ( " update item set item_flags = ( item_flags & ~%d ) where parent = %d and uid = %d " ,
intval ( ITEM_UNSEEN ),
intval ( $_REQUEST [ 'markItemRead' ]),
intval ( local_user ())
);
}
2014-07-01 00:03:00 +00:00
/**
* URL ping / something will return detail for " something " , e . g . a json list with which to populate a notification
* dropdown menu .
*/
2012-08-30 06:03:03 +00:00
if ( argc () > 1 && argv ( 1 ) === 'notify' ) {
2012-03-01 00:26:07 +00:00
$t = q ( " select count(*) as total from notify where uid = %d and seen = 0 " ,
2012-02-22 03:03:55 +00:00
intval ( local_user ())
);
2012-03-01 00:26:07 +00:00
if ( $t && intval ( $t [ 0 ][ 'total' ]) > 49 ) {
$z = q ( " select * from notify where uid = %d
PostgreSQL support initial commit
There were 11 main types of changes:
- UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but
it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just
copied from Friendica. All of these instances, the LIMIT 1 was simply removed.
- Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit
integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice
to boot). Proper explicit boolean conversions were added. New queries should use proper conventions.
- MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_
func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There
were no true toggles (XOR). New queries should refrain from using XOR when not necessary.
- There are several fields which the schema has marked as NOT NULL, but the inserts don't specify
them. The reason this works is because mysql totally ignores the constraint and adds an empty text
default automatically. Again, non-compliant, obviously. In these cases a default of empty text was
added.
- Several statements rely on a non-standard MySQL feature
(http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten
to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run
a zillion times faster, even on MySQL.
- A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG,
UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_
- INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes
around the value -- assist functions added in the dba_
- NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such
thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are
handled in Zot/item packets automagically by quoting all dates with dbescdate().
- char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the
code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works
better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype
for all text fields in the postgres schema. varchar was used in a couple of places where it actually
seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code
actually validates data, new bugs might come out from under the rug.
- postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted.
bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function
was added to handle this transparently.
- postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax.
Statements were updated to be standard.
These changes require corresponding changes in the coding standards. Please review those before
adding any code going forward.
Still on my TODO list:
- remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting
- Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
and seen = 0 order by date desc limit 50 " ,
2012-03-01 00:26:07 +00:00
intval ( local_user ())
);
}
else {
$z1 = q ( " select * from notify where uid = %d
PostgreSQL support initial commit
There were 11 main types of changes:
- UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but
it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just
copied from Friendica. All of these instances, the LIMIT 1 was simply removed.
- Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit
integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice
to boot). Proper explicit boolean conversions were added. New queries should use proper conventions.
- MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_
func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There
were no true toggles (XOR). New queries should refrain from using XOR when not necessary.
- There are several fields which the schema has marked as NOT NULL, but the inserts don't specify
them. The reason this works is because mysql totally ignores the constraint and adds an empty text
default automatically. Again, non-compliant, obviously. In these cases a default of empty text was
added.
- Several statements rely on a non-standard MySQL feature
(http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten
to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run
a zillion times faster, even on MySQL.
- A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG,
UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_
- INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes
around the value -- assist functions added in the dba_
- NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such
thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are
handled in Zot/item packets automagically by quoting all dates with dbescdate().
- char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the
code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works
better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype
for all text fields in the postgres schema. varchar was used in a couple of places where it actually
seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code
actually validates data, new bugs might come out from under the rug.
- postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted.
bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function
was added to handle this transparently.
- postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax.
Statements were updated to be standard.
These changes require corresponding changes in the coding standards. Please review those before
adding any code going forward.
Still on my TODO list:
- remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting
- Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
and seen = 0 order by date desc limit 50 " ,
2012-03-01 00:26:07 +00:00
intval ( local_user ())
);
$z2 = q ( " select * from notify where uid = %d
PostgreSQL support initial commit
There were 11 main types of changes:
- UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but
it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just
copied from Friendica. All of these instances, the LIMIT 1 was simply removed.
- Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit
integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice
to boot). Proper explicit boolean conversions were added. New queries should use proper conventions.
- MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_
func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There
were no true toggles (XOR). New queries should refrain from using XOR when not necessary.
- There are several fields which the schema has marked as NOT NULL, but the inserts don't specify
them. The reason this works is because mysql totally ignores the constraint and adds an empty text
default automatically. Again, non-compliant, obviously. In these cases a default of empty text was
added.
- Several statements rely on a non-standard MySQL feature
(http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten
to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run
a zillion times faster, even on MySQL.
- A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG,
UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_
- INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes
around the value -- assist functions added in the dba_
- NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such
thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are
handled in Zot/item packets automagically by quoting all dates with dbescdate().
- char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the
code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works
better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype
for all text fields in the postgres schema. varchar was used in a couple of places where it actually
seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code
actually validates data, new bugs might come out from under the rug.
- postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted.
bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function
was added to handle this transparently.
- postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax.
Statements were updated to be standard.
These changes require corresponding changes in the coding standards. Please review those before
adding any code going forward.
Still on my TODO list:
- remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting
- Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
and seen = 1 order by date desc limit % d " ,
2012-03-01 00:26:07 +00:00
intval ( local_user ()),
intval ( 50 - intval ( $t [ 0 ][ 'total' ]))
);
$z = array_merge ( $z1 , $z2 );
}
2012-07-13 14:09:29 +00:00
if ( count ( $z )) {
foreach ( $z as $zz ) {
$notifs [] = array (
'notify_link' => $a -> get_baseurl () . '/notify/view/' . $zz [ 'id' ],
2013-02-11 03:34:02 +00:00
'name' => '' , // not required here because the name is in the message
2012-07-13 14:09:29 +00:00
'url' => $zz [ 'url' ],
'photo' => $zz [ 'photo' ],
'when' => relative_date ( $zz [ 'date' ]),
2014-11-10 22:23:06 +00:00
'hclass' => (( $zz [ 'seen' ]) ? 'notify-seen' : 'notify-unseen' ),
2012-07-13 14:09:29 +00:00
'message' => strip_tags ( bbcode ( $zz [ 'msg' ]))
);
2011-09-28 07:30:22 +00:00
}
2011-08-23 11:52:20 +00:00
}
2012-07-13 14:09:29 +00:00
echo json_encode ( array ( 'notify' => $notifs ));
killme ();
}
2012-10-27 11:43:39 +00:00
2013-01-08 10:49:08 +00:00
if ( argc () > 1 && argv ( 1 ) === 'messages' ) {
$channel = $a -> get_channel ();
$t = q ( " select mail.*, xchan.* from mail left join xchan on xchan_hash = from_xchan
PostgreSQL support initial commit
There were 11 main types of changes:
- UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but
it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just
copied from Friendica. All of these instances, the LIMIT 1 was simply removed.
- Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit
integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice
to boot). Proper explicit boolean conversions were added. New queries should use proper conventions.
- MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_
func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There
were no true toggles (XOR). New queries should refrain from using XOR when not necessary.
- There are several fields which the schema has marked as NOT NULL, but the inserts don't specify
them. The reason this works is because mysql totally ignores the constraint and adds an empty text
default automatically. Again, non-compliant, obviously. In these cases a default of empty text was
added.
- Several statements rely on a non-standard MySQL feature
(http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten
to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run
a zillion times faster, even on MySQL.
- A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG,
UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_
- INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes
around the value -- assist functions added in the dba_
- NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such
thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are
handled in Zot/item packets automagically by quoting all dates with dbescdate().
- char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the
code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works
better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype
for all text fields in the postgres schema. varchar was used in a couple of places where it actually
seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code
actually validates data, new bugs might come out from under the rug.
- postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted.
bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function
was added to handle this transparently.
- postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax.
Statements were updated to be standard.
These changes require corresponding changes in the coding standards. Please review those before
adding any code going forward.
Still on my TODO list:
- remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting
- Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
where channel_id = % d and not ( mail_flags & % d ) > 0 and not ( mail_flags & % d ) > 0
and from_xchan != '%s' order by created desc limit 50 " ,
2013-01-08 10:49:08 +00:00
intval ( local_user ()),
intval ( MAIL_SEEN ),
intval ( MAIL_DELETED ),
dbesc ( $channel [ 'channel_hash' ])
);
if ( $t ) {
foreach ( $t as $zz ) {
$notifs [] = array (
2013-12-22 07:47:44 +00:00
'notify_link' => $a -> get_baseurl () . '/mail/' . $zz [ 'id' ],
2013-01-08 10:49:08 +00:00
'name' => $zz [ 'xchan_name' ],
'url' => $zz [ 'xchan_url' ],
'photo' => $zz [ 'xchan_photo_s' ],
'when' => relative_date ( $zz [ 'created' ]),
2014-11-10 22:23:06 +00:00
'hclass' => (( $zz [ 'mail_flags' ] & MAIL_SEEN ) ? 'notify-seen' : 'notify-unseen' ),
2013-01-08 10:49:08 +00:00
'message' => t ( 'sent you a private message' ),
);
}
}
echo json_encode ( array ( 'notify' => $notifs ));
killme ();
}
2012-10-27 11:43:39 +00:00
if ( argc () > 1 && ( argv ( 1 ) === 'network' || argv ( 1 ) === 'home' )) {
$result = array ();
2012-12-02 23:45:13 +00:00
2012-11-30 04:46:45 +00:00
$r = q ( " SELECT * FROM item
PostgreSQL support initial commit
There were 11 main types of changes:
- UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but
it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just
copied from Friendica. All of these instances, the LIMIT 1 was simply removed.
- Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit
integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice
to boot). Proper explicit boolean conversions were added. New queries should use proper conventions.
- MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_
func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There
were no true toggles (XOR). New queries should refrain from using XOR when not necessary.
- There are several fields which the schema has marked as NOT NULL, but the inserts don't specify
them. The reason this works is because mysql totally ignores the constraint and adds an empty text
default automatically. Again, non-compliant, obviously. In these cases a default of empty text was
added.
- Several statements rely on a non-standard MySQL feature
(http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten
to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run
a zillion times faster, even on MySQL.
- A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG,
UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_
- INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes
around the value -- assist functions added in the dba_
- NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such
thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are
handled in Zot/item packets automagically by quoting all dates with dbescdate().
- char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the
code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works
better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype
for all text fields in the postgres schema. varchar was used in a couple of places where it actually
seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code
actually validates data, new bugs might come out from under the rug.
- postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted.
bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function
was added to handle this transparently.
- postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax.
Statements were updated to be standard.
These changes require corresponding changes in the coding standards. Please review those before
adding any code going forward.
Still on my TODO list:
- remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting
- Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
WHERE item_restrict = % d and ( item_flags & % d ) > 0 and uid = % d " ,
2012-10-27 11:43:39 +00:00
intval ( ITEM_VISIBLE ),
intval ( ITEM_UNSEEN ),
intval ( local_user ())
);
2012-12-02 23:45:13 +00:00
2012-10-27 11:43:39 +00:00
if ( $r ) {
2012-11-14 00:04:22 +00:00
xchan_query ( $r );
2012-10-27 11:43:39 +00:00
foreach ( $r as $item ) {
2012-11-30 04:46:45 +00:00
if (( argv ( 1 ) === 'home' ) && ( ! ( $item [ 'item_flags' ] & ITEM_WALL )))
2012-10-27 11:43:39 +00:00
continue ;
$result [] = format_notification ( $item );
}
2014-06-30 20:16:21 +00:00
}
logger ( 'ping (network||home): ' . print_r ( $result , true ), LOGGER_DATA );
2013-01-08 19:59:29 +00:00
echo json_encode ( array ( 'notify' => $result ));
2012-10-27 11:43:39 +00:00
killme ();
}
2013-01-10 07:07:13 +00:00
if ( argc () > 1 && ( argv ( 1 ) === 'intros' )) {
2012-12-02 23:45:13 +00:00
$result = array ();
PostgreSQL support initial commit
There were 11 main types of changes:
- UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but
it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just
copied from Friendica. All of these instances, the LIMIT 1 was simply removed.
- Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit
integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice
to boot). Proper explicit boolean conversions were added. New queries should use proper conventions.
- MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_
func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There
were no true toggles (XOR). New queries should refrain from using XOR when not necessary.
- There are several fields which the schema has marked as NOT NULL, but the inserts don't specify
them. The reason this works is because mysql totally ignores the constraint and adds an empty text
default automatically. Again, non-compliant, obviously. In these cases a default of empty text was
added.
- Several statements rely on a non-standard MySQL feature
(http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten
to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run
a zillion times faster, even on MySQL.
- A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG,
UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_
- INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes
around the value -- assist functions added in the dba_
- NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such
thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are
handled in Zot/item packets automagically by quoting all dates with dbescdate().
- char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the
code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works
better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype
for all text fields in the postgres schema. varchar was used in a couple of places where it actually
seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code
actually validates data, new bugs might come out from under the rug.
- postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted.
bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function
was added to handle this transparently.
- postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax.
Statements were updated to be standard.
These changes require corresponding changes in the coding standards. Please review those before
adding any code going forward.
Still on my TODO list:
- remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting
- Rewrite search queries for better results (both MySQL and Postgres)
2014-11-13 20:21:58 +00:00
$r = q ( " SELECT * FROM abook left join xchan on abook.abook_xchan = xchan.xchan_hash where abook_channel = %d and (abook_flags & %d)>0 and not ((abook_flags & %d)>0 or (xchan_flags & %d)>0) " ,
2012-12-02 23:45:13 +00:00
intval ( local_user ()),
intval ( ABOOK_FLAG_PENDING ),
2014-07-06 04:45:13 +00:00
intval ( ABOOK_FLAG_SELF | ABOOK_FLAG_IGNORED ),
intval ( XCHAN_FLAGS_DELETED | XCHAN_FLAGS_ORPHAN )
2012-12-02 23:45:13 +00:00
);
if ( $r ) {
foreach ( $r as $rr ) {
$result [] = array (
2014-01-08 19:32:06 +00:00
'notify_link' => $a -> get_baseurl () . '/connedit/' . $rr [ 'abook_id' ],
2012-12-02 23:45:13 +00:00
'name' => $rr [ 'xchan_name' ],
'url' => $rr [ 'xchan_url' ],
'photo' => $rr [ 'xchan_photo_s' ],
'when' => relative_date ( $rr [ 'abook_created' ]),
2014-11-10 22:23:06 +00:00
'hclass' => ( 'notify-unseen' ),
2013-01-10 07:07:13 +00:00
'message' => t ( 'added your channel' )
2012-12-02 23:45:13 +00:00
);
}
2014-06-30 20:16:21 +00:00
}
logger ( 'ping (intros): ' . print_r ( $result , true ), LOGGER_DATA );
2013-01-10 07:07:13 +00:00
echo json_encode ( array ( 'notify' => $result ));
2012-12-02 23:45:13 +00:00
killme ();
}
2013-01-16 10:01:23 +00:00
if ( argc () > 1 && ( argv ( 1 ) === 'all_events' )) {
2013-01-16 11:18:32 +00:00
$bd_format = t ( 'g A l F d' ) ; // 8 AM Friday January 18
2013-01-16 10:01:23 +00:00
$result = array ();
$r = q ( " SELECT * FROM event left join xchan on event_xchan = xchan_hash
WHERE `event` . `uid` = % d AND start < '%s' AND start > '%s' and `ignore` = 0
ORDER BY `start` DESC " ,
intval ( local_user ()),
2014-11-04 23:24:24 +00:00
dbesc ( datetime_convert ( 'UTC' , date_default_timezone_get (), 'now + ' . intval ( $evdays ) . ' days' )),
2014-06-30 20:16:21 +00:00
dbesc ( datetime_convert ( 'UTC' , date_default_timezone_get (), 'now - 1 days' ))
2013-01-16 10:01:23 +00:00
);
if ( $r ) {
foreach ( $r as $rr ) {
2013-01-16 11:18:32 +00:00
if ( $rr [ 'adjust' ])
2014-06-30 20:16:21 +00:00
$md = datetime_convert ( 'UTC' , date_default_timezone_get (), $rr [ 'start' ], 'Y/m' );
2013-01-16 11:18:32 +00:00
else
2014-06-30 20:16:21 +00:00
$md = datetime_convert ( 'UTC' , 'UTC' , $rr [ 'start' ], 'Y/m' );
2013-01-16 11:18:32 +00:00
2014-07-01 00:03:00 +00:00
$strt = datetime_convert ( 'UTC' , (( $rr [ 'adjust' ]) ? date_default_timezone_get () : 'UTC' ), $rr [ 'start' ]);
2014-06-30 20:16:21 +00:00
$today = (( substr ( $strt , 0 , 10 ) === datetime_convert ( 'UTC' , date_default_timezone_get (), 'now' , 'Y-m-d' )) ? true : false );
2013-01-16 11:18:32 +00:00
2014-07-01 00:03:00 +00:00
$when = day_translate ( datetime_convert ( 'UTC' , (( $rr [ 'adjust' ]) ? date_default_timezone_get () : 'UTC' ), $rr [ 'start' ], $bd_format )) . (( $today ) ? ' ' . t ( '[today]' ) : '' );
2013-01-16 11:18:32 +00:00
2013-01-16 10:01:23 +00:00
$result [] = array (
2013-11-13 22:18:07 +00:00
'notify_link' => $a -> get_baseurl () . '/events' , // FIXME this takes you to an edit page and it may not be yours, we really want to just view the single event --> '/events/event/' . $rr['event_hash'],
2013-01-16 10:01:23 +00:00
'name' => $rr [ 'xchan_name' ],
'url' => $rr [ 'xchan_url' ],
'photo' => $rr [ 'xchan_photo_s' ],
2013-01-16 11:18:32 +00:00
'when' => $when ,
2014-11-10 22:23:06 +00:00
'hclass' => ( 'notify-unseen' ),
2013-01-16 10:01:23 +00:00
'message' => t ( 'posted an event' )
);
}
2014-06-30 20:16:21 +00:00
}
logger ( 'ping (all_events): ' . print_r ( $result , true ), LOGGER_DATA );
2013-01-16 10:01:23 +00:00
echo json_encode ( array ( 'notify' => $result ));
killme ();
}
2014-07-01 00:03:00 +00:00
/**
* Normal ping - just the counts , no detail
*/
2014-11-04 23:24:24 +00:00
if ( $vnotify & VNOTIFY_SYSTEM ) {
$t = q ( " select count(*) as total from notify where uid = %d and seen = 0 " ,
intval ( local_user ())
);
if ( $t )
$result [ 'notify' ] = intval ( $t [ 0 ][ 'total' ]);
}
2012-07-13 14:09:29 +00:00
2012-07-26 05:55:43 +00:00
$t1 = dba_timer ();
2014-11-04 23:24:24 +00:00
if ( $vnotify & ( VNOTIFY_NETWORK | VNOTIFY_CHANNEL )) {
$r = q ( " SELECT id, item_restrict, item_flags FROM item
2014-11-13 21:06:31 +00:00
WHERE ( item_restrict = % d ) and ( item_flags & % d ) > 0 and uid = % d " ,
2014-11-04 23:24:24 +00:00
intval ( ITEM_VISIBLE ),
intval ( ITEM_UNSEEN ),
intval ( local_user ())
);
2012-07-13 14:09:29 +00:00
2014-11-04 23:24:24 +00:00
if ( $r ) {
$arr = array ( 'items' => $r );
call_hooks ( 'network_ping' , $arr );
2012-09-28 00:48:10 +00:00
2014-11-04 23:24:24 +00:00
foreach ( $r as $it ) {
if ( $it [ 'item_flags' ] & ITEM_WALL )
$result [ 'home' ] ++ ;
else
$result [ 'network' ] ++ ;
}
2011-09-28 07:30:22 +00:00
}
2012-07-13 14:09:29 +00:00
}
2014-11-04 23:24:24 +00:00
if ( ! ( $vnotify & VNOTIFY_NETWORK ))
$result [ 'network' ] = 0 ;
if ( ! ( $vnotify & VNOTIFY_CHANNEL ))
$result [ 'home' ] = 0 ;
2011-08-17 19:59:06 +00:00
2012-07-26 05:55:43 +00:00
$t2 = dba_timer ();
2014-11-04 23:24:24 +00:00
if ( $vnotify & VNOTIFY_INTRO ) {
2014-11-13 21:06:31 +00:00
$intr = q ( " SELECT COUNT(abook.abook_id) AS total FROM abook left join xchan on abook.abook_xchan = xchan.xchan_hash where abook_channel = %d and (abook_flags & %d)>0 and not ((abook_flags & %d)>0 or (xchan_flags & %d)>0) " ,
2014-11-04 23:24:24 +00:00
intval ( local_user ()),
intval ( ABOOK_FLAG_PENDING ),
intval ( ABOOK_FLAG_SELF | ABOOK_FLAG_IGNORED ),
intval ( XCHAN_FLAGS_DELETED | XCHAN_FLAGS_ORPHAN )
);
2012-07-26 05:55:43 +00:00
2014-11-04 23:24:24 +00:00
$t3 = dba_timer ();
2012-07-26 05:55:43 +00:00
2014-11-04 23:24:24 +00:00
if ( $intr )
$result [ 'intros' ] = intval ( $intr [ 0 ][ 'total' ]);
}
2012-07-13 14:09:29 +00:00
2012-07-26 05:55:43 +00:00
$t4 = dba_timer ();
2012-12-05 02:24:46 +00:00
$channel = get_app () -> get_channel ();
2012-07-26 05:55:43 +00:00
2014-11-04 23:24:24 +00:00
if ( $vnotify & VNOTIFY_MAIL ) {
$mails = q ( " SELECT count(id) as total from mail
2014-11-13 21:06:31 +00:00
WHERE channel_id = % d AND not ( mail_flags & % d ) > 0 and from_xchan != '%s' " ,
2014-11-04 23:24:24 +00:00
intval ( local_user ()),
intval ( MAIL_SEEN ),
dbesc ( $channel [ 'channel_hash' ])
2013-02-09 21:20:10 +00:00
);
2014-11-04 23:24:24 +00:00
if ( $mails )
$result [ 'mail' ] = intval ( $mails [ 0 ][ 'total' ]);
}
if ( $vnotify & VNOTIFY_REGISTER ) {
if ( $a -> config [ 'system' ][ 'register_policy' ] == REGISTER_APPROVE && is_site_admin ()) {
2014-11-13 21:06:31 +00:00
$regs = q ( " SELECT count(account_id) as total from account where (account_flags & %d)>0 " ,
2014-11-04 23:24:24 +00:00
intval ( ACCOUNT_PENDING )
);
if ( $regs )
$result [ 'register' ] = intval ( $regs [ 0 ][ 'total' ]);
}
2012-07-13 14:09:29 +00:00
}
2012-07-26 05:55:43 +00:00
$t5 = dba_timer ();
2014-11-04 23:24:24 +00:00
if ( $vnotify & ( VNOTIFY_EVENT | VNOTIFY_EVENTTODAY | VNOTIFY_BIRTHDAY )) {
$events = q ( " SELECT type, start, adjust FROM `event`
WHERE `event` . `uid` = % d AND start < '%s' AND start > '%s' and `ignore` = 0
ORDER BY `start` ASC " ,
intval ( local_user ()),
dbesc ( datetime_convert ( 'UTC' , date_default_timezone_get (), 'now + ' . intval ( $evdays ) . ' days' )),
dbesc ( datetime_convert ( 'UTC' , date_default_timezone_get (), 'now - 1 days' ))
);
if ( $events ) {
$result [ 'all_events' ] = count ( $events );
if ( $result [ 'all_events' ]) {
$str_now = datetime_convert ( 'UTC' , date_default_timezone_get (), 'now' , 'Y-m-d' );
foreach ( $events as $x ) {
$bd = false ;
if ( $x [ 'type' ] === 'birthday' ) {
$result [ 'birthdays' ] ++ ;
$bd = true ;
}
else {
$result [ 'events' ] ++ ;
}
if ( datetime_convert ( 'UTC' , (( intval ( $x [ 'adjust' ])) ? date_default_timezone_get () : 'UTC' ), $x [ 'start' ], 'Y-m-d' ) === $str_now ) {
$result [ 'all_events_today' ] ++ ;
if ( $bd )
$result [ 'birthdays_today' ] ++ ;
else
$result [ 'events_today' ] ++ ;
}
2012-08-17 06:11:24 +00:00
}
2012-07-29 00:39:26 +00:00
}
}
}
2014-11-04 23:24:24 +00:00
if ( ! ( $vnotify & VNOTIFY_EVENT ))
$result [ 'all_events' ] = $result [ 'events' ] = 0 ;
if ( ! ( $vnotify & VNOTIFY_EVENTTODAY ))
$result [ 'all_events_today' ] = $result [ 'events_today' ] = 0 ;
if ( ! ( $vnotify & VNOTIFY_BIRTHDAY ))
$result [ 'birthdays' ] = 0 ;
2012-07-29 00:39:26 +00:00
2012-07-26 05:55:43 +00:00
$x = json_encode ( $result );
2011-09-05 12:01:21 +00:00
2012-07-26 05:55:43 +00:00
$t6 = dba_timer ();
// logger('ping timer: ' . sprintf('%01.4f %01.4f %01.4f %01.4f %01.4f %01.4f',$t6 - $t5, $t5 - $t4, $t4 - $t3, $t3 - $t2, $t2 - $t1, $t1 - $t0));
echo $x ;
2010-07-20 05:52:31 +00:00
killme ();
}
