Sponsored Content
Special Forums UNIX and Linux Applications Choosing DBMS for sensor network like system Post 302637517 by majid.merkava on Wednesday 9th of May 2012 02:11:07 AM
Old 05-09-2012
That's why we are getting problem and I'm looking for a good dbms for this case. I think relational DB are not suitable for us. I'm considering to use MongoDB.
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Network and System files

I was given this question and cannot seem to answer it. "Identify 4 network and 4 sytem files that control how the system and network function (other than rc files)." The problem is I only know of rc files. Can anyone help? (2 Replies)
Discussion started by: trip
2 Replies

2. Shell Programming and Scripting

Taking a system off a network on a system

say i have a system on thats on a network with access to the internet. now, i have sensitive information on this system and i do not want the system to be connected to the outside world anymore. how do i get it off the network without actually having to disconnect the cables? i'm asking this... (4 Replies)
Discussion started by: Terrible
4 Replies

3. Linux

network audio system

The Network Audio System (NAS) Anybody have any luck with nasd or xmms-nas with any 2.6 distribution? Works fine under FreeBSD (6.0/7.0). (0 Replies)
Discussion started by: ramen_noodle
0 Replies

4. SCO

Ingres dbms on sco unix

Hi everybody. I'm going to install ingres on sco unix 5.0.7. A client version may be usefull. I want to know how can I get appropriate version and how to install ingres on sco unix. thanks. (1 Reply)
Discussion started by: javad1_maroofi
1 Replies

5. AIX

Network File System using HACMP

Hi, I have an HACMP cluster with two nodes. The Resource Group contains a VG which in turn has a FS created in it say /test.. Now I want that FS to be mounted through NFS on some other AIX servers as well. What would be the best way to do this? Regards, (2 Replies)
Discussion started by: aixromeo
2 Replies
MONGODB(3)								 1								MONGODB(3)

The MongoDB class

INTRODUCTION
Instances of this class are used to interact with a database. To get a database: Example #1 Selecting a database <?php $m = new MongoClient(); // connect $db = $m->selectDB("example"); ?> Database names can use almost any character in the ASCII range. However, they cannot contain " ", "." or be the empty string. The name "system" is also reserved. A few unusual, but valid, database names: "null", "[x,y]", "3", """, "/". Unlike collection names, database names may contain "$". CLASS SYNOPSIS
MongoDB MongoDB Constants o const int$MongoDB::PROFILING_OFF0 o const int$MongoDB::PROFILING_SLOW1 o const int$MongoDB::PROFILING_ON2 Fields o public integer$w1 o public integer$wtimeout10000 Methods o public array MongoDB::authenticate (string $username, string $password) o public array MongoDB::command (array $command, [array $options = array()], [string &$hash]) o public MongoDB::__construct (MongoClient $conn, string $name) o public MongoCollection MongoDB::createCollection (string $name, [array $options]) o public array MongoDB::createDBRef (string $collection, mixed $document_or_id) o public array MongoDB::drop (void ) o public array MongoDB::dropCollection (mixed $coll) o public array MongoDB::execute (mixed $code, [array $args = array()]) o public bool MongoDB::forceError (void ) o public MongoCollection MongoDB::__get (string $name) o public array MongoDB::getCollectionInfo ([array $options = array()]) o public array MongoDB::getCollectionNames ([array $options = array()]) o public array MongoDB::getDBRef (array $ref) o public MongoGridFS MongoDB::getGridFS ([string $prefix = "fs"]) o public int MongoDB::getProfilingLevel (void ) o public array MongoDB::getReadPreference (void ) o public bool MongoDB::getSlaveOkay (void ) o public array MongoDB::getWriteConcern (void ) o public array MongoDB::lastError (void ) o public array MongoDB::listCollections ([array $options = array()]) o public array MongoDB::prevError (void ) o public array MongoDB::repair FALSE FALSE ([bool $preserve_cloned_files], [bool $backup_original_files]) o public array MongoDB::resetError (void ) o public MongoCollection MongoDB::selectCollection (string $name) o public int MongoDB::setProfilingLevel (int $level) o public bool MongoDB::setReadPreference (string $read_preference, [array $tags]) o public bool MongoDB::setSlaveOkay ([bool $ok = true]) o public bool MongoDB::setWriteConcern (mixed $w, [int $wtimeout]) o public string MongoDB::__toString (void ) PREDEFINED CONSTANTS
MONGODB LOG LEVELS
o MongoDB::PROFILING_OFF - 0 - Profiling is off. o MongoDB::PROFILING_SLOW - 1 - Profiling is on for slow operations (>100 ms). o MongoDB::PROFILING_ON - 2 - Profiling is on for all operations. FIELDS
o $w -1 - The number of servers to replicate a change to before returning success. Inherited by instances of MongoCollection derived from this. w functionality is only available in version 1.5.1+ of the MongoDB server and 1.0.8+ of the driver. w is used when- ever you need to adjust the acknowledgement level (MongoCollection.insert(3), MongoCollection.update(3), MongoCollec- tion.remove(3), MongoCollection.save(3), and MongoCollection.ensureIndex(3) all support this option). With the default value (1), an acknowledged operation will return once the database server has the operation. If the server goes down before the operation has been replicated to a secondary, it is possible to lose the operation forever. Thus, you can specify w to be higher than one and guarantee that at least one secondary has the operation before it is considered successful. For example, if w is 2, the primary and one secondary must have a record of the operation or the driver will throw a MongoCursorException. It is tempting to set w to the total number of secondaries + primary, but then if one secondary is down the operation will fail and an exception will be thrown, so usually w=2 is safest (primary and one secondary). o $wtimeout -10000 - The number of milliseconds to wait for MongoDB::$w replications to take place. Inherited by instances of MongoCollection derived from this. w functionality is only available in version 1.5.1+ of the MongoDB server and 1.0.8+ of the driver. Unless wtimeout is set, the server waits forever for replicating to w servers to finish. The driver defaults to waiting for 10 seconds, you can change this value to alter its behavior. SEE ALSO
MongoDB core docs on databases. PHP Documentation Group MONGODB(3)
All times are GMT -4. The time now is 04:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy