Error Creating Persisted Connection File
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 242 Star 4,617 Fork 463 paralect/robomongo Code Issues 318 mysql_connect Pull requests 6 Projects 1 Wiki Pulse Graphs New issue No
Phpmyadmin
errors logged if settings directory cannot be created or settings file cannot be written to #636 xampp Closed hansod1 opened this Issue Aug 13, 2014 · 8 comments Projects None yet Labels bug Milestone Robomongo 0.8.5 Assignees stennie 2 participants hansod1 commented Aug 13, 2014 Platform: OSX 10.9.4 Robomongo: 0.8.4 1.) Start Robomongo 2.) Create a new connection 3.) Successfully connect, run queries, etc. 4.) Close Robomongo 5.) Restart Robomongo I expect: That the connection created in step 2 still exists, and I can select it and connect again. Instead: The connection created in step 2 is not present, and I need to re-create the connection in order to connect to my database. Am I doing something wrong here? Is this a feature, and not a bug? stennie added the duplicate label Aug 13, 2014 stennie commented Aug 13, 2014 @hansod1 Robomongo 0.8.4 saves the connection settings in the "MongoDB Connections" list, but does not save/restore the list of tabs you have open. There's an open feature request for this: #340. stennie closed this Aug 13, 2014 hansod1 commented Aug 13, 2014 What I'm experiencing is exactly the opposite of what you just said. Robomongo does not save the connection settings in the "MongoDB Connections" list. At least not for me. stennie commented Aug 13, 2014 @hansod1 FYI, I missed a "not" in my comment (the tabs are not saved). If the connection settings aren't saved, that's definitely unexpected behaviour. Any saved settings are written to a robomongo.json file in your $HOME/.config/robomongo directory. Can you include the outp
Generators References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting Using Register Globals User Submitted Data Magic Quotes Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Dealing with XForms Handling file uploads Using remote files Connection handling Persistent Database Connections Safe Mode Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour https://github.com/paralect/robomongo/issues/636 Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Credit Card Processing Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server http://php.net/manual/en/features.persistent-connections.php Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation Keyboard Shortcuts? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search(current page) / Focus search box Safe Mode » « Connection handling PHP Manual Features Change language: English Brazilian Portuguese Chinese (Simplified) French German Japanese Korean Romanian Russian Spanish Turkish Other Edit Report a Bug Persistent Database Connections Persistent connections are links that do not close when the execution of your script ends. When a persistent connection is requested, PHP checks if there's already an identical persistent connection (that remained open from earlier) - and if it exists, it uses it. If it does not exist, it creates the link. An 'identical' connection is a connection that was opened to the same host, with the same username and the same password (where applicable). People who aren't tho