Sponsored Content
Top Forums Web Development Notes with Ravinder on Badging System Development Part II Post 303028191 by Neo on Tuesday 1st of January 2019 01:04:01 PM
Old 01-01-2019
Hey Ravinder.

If I were you, I would do this query:

Code:
mysql> select joindate from user where userid =1;

Take that result subtracted from today in UNIXTIME and divide by the number of seconds in year.

That gives you the number of years a person has been a member.

You don't need that fancy MySQL query with all the date / time functions for such a trivial requirement.

As you are beginner in programming, keep it simple... well, I suggest you keep it simple all your life; it's easier to debug or change when you look at the code in 10 years..... keep it simple. Do not be seduced by fancy queries and logic which look cool.... like many programmers and tech people do.

Keep it simple so that a 10th grader can understand it.
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

New Badging System - Badges Prototype Beta 1 (Badges Only)

Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid: https://www.unix.com/members/1-albums215-picture991.png The prototype HTML code for this layout: <style> .fa-badge-grid { font-size: 1.5em; } .row { ... (38 Replies)
Discussion started by: Neo
38 Replies

2. What is on Your Mind?

Status of Badging System - Beta 1

Dear All, Here is the current status of the badging system: The Beta 1 phase of the new badging system is close to completion. 42 prototype badges have been "allocated" 6 prototype badge slots are held in reserve The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies

3. What is on Your Mind?

Badging System: UNIX.COM Bug Hunter Badge (New)

I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far,... (0 Replies)
Discussion started by: Neo
0 Replies
MYSQLND_MEMCACHE_SET(3) 						 1						   MYSQLND_MEMCACHE_SET(3)

mysqlnd_memcache_set - Associate a MySQL connection with a Memcache connection

SYNOPSIS
bool mysqlnd_memcache_set (mixed $mysql_connection, [Memcached $memcache_connection], [string $pattern], [callback $callback]) DESCRIPTION
Associate $mysql_connection with $memcache_connection using $pattern as a PCRE regular expression, and $callback as a notification call- back or to unset the association of $mysql_connection. While associating a MySQL connection with a Memcache connection, this function will query the MySQL Server for its configuration. It will automatically detect whether the server is configured to use the InnoDB Memcache Daemon Plugin or MySQL Cluster NDB Memcache support. It will also query the server to automatically identify exported tables and other configuration options. The results of this automatic config- uration can be retrieved using mysqlnd_memcache_get_config(3). PARAMETERS
o $mysql_connection - A handle to a MySQL Server using one of the MySQL API extensions for PHP, which are PDO_MYSQL, mysqli or ext/mysql. o $memcache_connection - A Memcached instance with a connection to the MySQL Memcache Daemon plugin. If this parameter is omitted, then $mysql_connection will be unassociated from any memcache connection. And if a previous association exists, then it will be replaced. o $pattern - A regular expression in Perl Compatible Regular Expression syntax used to identify potential Memcache-queries. The query should have three sub patterns. The first subpattern contains the requested field list, the second the name of the ID column from the query and the third the requested value. If this parameter is omitted or os set to NULL, then a default pattern will be used. o $callback - A callback which will be used whenever a query is being sent to MySQL. The callback will receive a single boolean parameter telling if a query was sent via Memcache. RETURN VALUES
TRUE if the association or disassociation is successful, otherwise FALSE if there is an error. EXAMPLES
Example #1 mysqlnd_memcache_set(3) example with var_dump(3) as a simple debugging callback. <?php $mysqli = new mysqli("host", "user", "passwd", "database"); $memc = new Memcached(); $memc->addServer("host", 11211); mysqlnd_memcache_set($mysqli, $memc, NULL, 'var_dump'); /* This query will be intercepted and executed via Memcache protocol */ echo "Sending query for id via Memcache: "; $mysqli->query("SELECT f1, f2, f3 FROM test WHERE id = 1"); /* f1 is not configured as valid key field, this won't be sent via Memcache */ echo "Sending query for f1 via Memcache: "; $mysqli->query("SELECT id FROM test WHERE f1 = 1"); mysqlnd_memcache_set($mysqli); /* Now the regular MySQL protocol will be used */ echo "var_dump won't be invoked: "; $mysqli->query("SELECT f1, f2, f3 WHERE id = 1"); ?> The above example will output: Sending query for id via Memcache: bool(true) Sending query for f1 via Memcache: bool(false) var_dump won't be invoked: SEE ALSO
mysqlnd_memcache_get_config(3). PHP Documentation Group MYSQLND_MEMCACHE_SET(3)
All times are GMT -4. The time now is 05:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy