- Moderated by:
- Support Team
Connect to Database
-
- rank:
-
Freshman
- registered:
- July 2006
- Status:
- offline
- last visit:
- 16.08.06
- Posts:
- 11
Normally you'd place a functions connecting to the database in the API. If you look at first.php you'll see it calling API functions several times. From line 107 in first.php:Code
// Call the modules API to get the items
$items = pnModAPIFunc('Example',
'user',
'getall');
This will call the Example_userapi_getall() function located in pnuserapi.php. If you open this file and locate the function you'll see that it's creating a connection to the database..
Code
$dbconn =& pnDBGetConn(true);
.. and later using that connection to execute SQL.
Code
$result = $dbconn->SelectLimit($sql, $numitems, $startnum-1);
If you don't need to set a limit you can also execute the SQL like this
Code
$result =& $dbconn->Execute($sql);
When you're done fetching the result you should close the result set before returning the data you were looking for
Code
$result->Close();
--
Erik from www.TenTonHammer.com
-
- rank:
-
Helper
- registered:
- January 2005
- Status:
- offline
- last visit:
- 29.10.08
- Posts:
- 312
Thanks for the great info. Is there any advantage to using PostNuke's method of connection to the database over using non-postnuke coding? i.e :
Code
edited by: sae, Jul 16, 2006 - 03:49 PM
-
- rank:
-
Freshman
- registered:
- July 2006
- Status:
- offline
- last visit:
- 16.08.06
- Posts:
- 11
It's generally a good idea to use core functions for security reasons, but it's also very practical.
You should at least not write that code in every function.. just imagine the nightmare if you one day have to change the password for example!
You could have that code in an own file and include it somehow, but why go through that stuff if you can just call the core function and be done with it? :)
--
Erik from www.TenTonHammer.com
|
