The problem seems to have been introduced in the latest version of ruby, ruby 2.2.0. Try this experiment: in rails console/or irb: [1] pry(main)>File.expand_path (“./”) => “/users/xxxx/Sites/xxxx” and in the terminal window: ]$ pwd /users/xxxx/sites/xxxx See the different case? If you get that, then deep in the bowels of active support a regex goes south. … Read more
If you replace j2ee by javaee, it will work fine. EDIT : <web-app version=”2.5″ xmlns=”http://java.sun.com/xml/ns/javaee” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd”> Edit: To know anything further related to this error. Please follow the Link. Here you will find schemas for Java EE deployment descriptors (web.xml).
Right click the Database and select Tasks -> Generate Scripts. You can you then select all the objects you require or only certain objects. There are some Script Options that you should look at: Script USE DATABASE – You should set this to false if you are creating a new database with a different name. … Read more
The KILL SESSION command doesn’t actually kill the session. It merely asks the session to kill itself. In some situations, like waiting for a reply from a remote database or rolling back transactions, the session will not kill itself immediately and will wait for the current operation to complete. In these cases the session will … Read more
You should take a look at pg_dump: pg_dump –schema-only databasename Will dump only the schema to stdout as .sql. For windows, you’ll probably want to call pg_dump.exe. I don’t have access to a Windows machine but I’m pretty sure from memory that’s the command. See if the help works for you too.
Edit – 20 March 2016 Mongoose now support timestamps for collections. Please consider the answer of @bobbyz below. Maybe this is what you are looking for. Original answer Mongoose supports a Date type (which is basically a timestamp): time : { type : Date, default: Date.now } With the above field definition, any time you … Read more
Good on you, for eliminating Nulls. I have never allowed Nulls in any of my databases. Of course, if nulls are prohibited, then missing information will have to be handled by some other means. Unfortunately, those other means are much too complex to be discussed in detail here. Actually it is not so hard at … Read more
How about the Materialized Path design? CREATE TABLE trie ( path VARCHAR(<maxdepth>) PRIMARY KEY, …other attributes of a tree node… ); To store a word like “stackoverflow”: INSERT INTO trie (path) VALUES (‘s’), (‘st’), (‘sta’), (‘stac’), (‘stack’), (‘stacko’), (‘stackov’), (‘stackove’), (‘stackover’), (‘stackover’), (‘stackoverf’), (‘stackoverflo’), (‘stackoverflow’); The materialized path in the tree is the prefixed sequence … Read more
I’ve noted 2 approaches to RESTful URI design: hierarchical & filtered I feel hierarchical is overly verbose, has the potential for redundant endpoints (not DRY) and disguises in what resource’s state you’re really interested (after all, REST = representational state transfer). I favor Simple URIs Simple is elegant. I’d choose a URI structure like GET … Read more
DO will do the trick: DO $$ DECLARE row record; BEGIN FOR row IN SELECT tablename FROM pg_tables WHERE schemaname=”public” — and other conditions, if needed LOOP EXECUTE format(‘ALTER TABLE public.%I SET SCHEMA [new_schema];’, row.tablename); END LOOP; END; $$;