arrow_back
Rewards And Recognition Dashboard
{{users.TotalPoints}}
Current Points Balance
Guild Group : {{users.column1}}
Level : Master
RootOrg
Guild Performance Metrics
H1 Stats
Dealership Sales CVP Index
{{metrics.H1.CVPIndex}}%
Sales Objective
{{metrics.H1.SalesObjective}}%
Sales Consultant Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Sales Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
H1 Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Retention Objective
{{metrics.H1.ServiceRetention}}%
Service Advisor Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
H1 Stats
Individual Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Technician Training (Self) :
{{metrics.H1.IndividualTrainingStatus}}%
Individual Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
H1 Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Trade Sales Objective
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
H1 Stats
Individual Sales CVP Index
{{metrics.H1.CVPIndex}}%
Individual Training Status
{{metrics.H1.SalesObjective}}%
Individual Sales Trust CVP Score :
{{metrics.H1.IndividualTrainingStatus}}
CX Process :
{{metrics.H1.QCStatus}}
H1 Stats
Individual Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Consultant Professional Training Mix
{{metrics.H1.TrainingMix}}%
Service Retention Objective
{{metrics.H1.ServiceRetention}}%
Individual Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
H1 Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Dealership Trade Sales/Parts Purchases Performance
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Training (Self) :
{{metrics.H1.IndividualTrainingStatus}}
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
H1 Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Dealership Sales CVP Index
{{metrics.H1.CVPIndex}}%
Dealership Trade Sales/Parts Purchases Performance
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Training (Self) :
{{metrics.H1.IndividualTrainingStatus}}
Sales Objective
{{metrics.H1.SalesObjective}}%
Service Retention Objective
{{metrics.H1.ServiceRetention}}%
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Dealership Sales Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
H2 Stats
Dealership Sales CVP Index
{{metrics.H1.CVPIndex}}%
Sales Objective
{{metrics.H1.SalesObjective}}%
Sales Consultant Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Sales Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
H2 Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Retention Objective
{{metrics.H1.ServiceRetention}}%
Service Advisor Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
H2 Stats
Individual Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Technician Training (Self) :
{{metrics.H1.IndividualTrainingStatus}}
Individual Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
H2 Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Trade Sales Objective
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
H2 Stats
Individual Sales CVP Index
{{metrics.H1.CVPIndex}}%
Individual Training Status :
{{metrics.H1.IndividualTrainingStatus}}
Individual Sales Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
H2 Stats
Individual Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Consultant Professional Training Mix
{{metrics.H1.TrainingMix}}%
Service Retention Objective
{{metrics.H1.ServiceRetention}}%
Individual Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
H2 Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Dealership Trade Sales/Parts Purchases Performance
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Training (Self)
{{metrics.H1.IndividualTrainingStatus}}
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
H2 Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Dealership Trade Sales/Parts Purchases Performance
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Training (Self)
{{metrics.H1.IndividualTrainingStatus}}
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
FY Stats
Dealership Sales CVP Index
{{metrics.H1.CVPIndex}}%
Sales Objective
{{metrics.H1.SalesObjective}}%
Sales Consultant Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Sales Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
FY Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Retention Objective
{{metrics.H1.ServiceRetention}}%
Service Advisor Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
H1 Stats
Individual Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Technician Training (Self)
{{metrics.H1.IndividualTrainingStatus}}
Individual Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
FY Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Trade Sales Objective
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Professional Training Mix
{{metrics.H1.TrainingMix}}%
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
FY Stats
Individual Sales CVP Index
{{metrics.H1.CVPIndex}}%
Individual Training Status
{{metrics.H1.IndividualTrainingStatus}}
Individual Sales Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
FY Stats
Individual Service CVP Index
{{metrics.H1.CVPIndex}}%
Service Consultant Professional Training Mix
{{metrics.H1.TrainingMix}}%
Service Retention Objective
{{metrics.H1.ServiceRetention}}%
Individual Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
CX Process :
{{metrics.H1.QCStatus}}
FY Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Dealership Trade Sales/Parts Purchases Performance
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Training (Self)
{{metrics.H1.IndividualTrainingStatus}}
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
FY Stats
Dealership Service CVP Index
{{metrics.H1.CVPIndex}}%
Dealership Trade Sales/Parts Purchases Performance
{{metrics.H1.SalesObjective}}%
Parts Sales Consultants Training (Self)
{{metrics.H1.IndividualTrainingStatus}}
Dealership Service Trust CVP Score :
{{metrics.H1.CVPTrust}}
Parts Group :
{{metrics.H1.partsGroup}}
info
There is no performance data
available for this sprint.


| DOSE: |
repeated |
|
Cocaine |
(powder / crystals) |
It started several months ago. I was sixteen at the time, living in New York state, and enjoying the summer before my junior year in high school started. Up until the first time I did coke my drug intake was limited, Mushrooms, alcohol, and weed were my expertise. I never saw myself as a cocaine user, I was all about tripping, smoking, and just partying around with friends. That all changed after my first few run-ins with cocaine.
Heaven. It may sound ridiculous but it is the only word to describe my first experience.  I can't say for sure how much I did, but I'd say I blew a half gram to my face that night. It was everything I wanted in a drug. It was subtle yet amazing. I could still function, but the euphoria and confidence boost was out of this world. I still remember that first drip, the taste almost made me throw-up, and yet I craved for it. I loved the numbness, I loved all the conversation it allowed, and I love flying 100mph in my friends Audi. I felt invinsible. Nothing could bring me down. I didn't have any bad come downs my first few times. I'm not sure why, but I guess it was due to the fact that I thought I found my dream drug.
The next couple weeks flew by faster than I ever thought possible. I was still smoking a lot of pot, and me and my friends would buy coke every friday to jump start our weekends. I thought coke was the bomb. At this time, it wasn't taking over my life, robbing my bank account, and rapping my personality... it was just a fun thing to do on the weekends.
Fast forward a couple weeks. Cocaine became an everyday thing. I would wake up, go to school, get out as early as possible, go to my dealers house, and blow lines with her. I was shocked to find out how many people in my school were into powder.  I still didn't care at this point in time.
School started back up and things started getting out of control. My bank account was gone. It's funny how fast you can spend thousands of dollars. I started chasing the high. I somehow managed to buy a half gram a day.  I could no longer breathe. I couldn't drink anything because there was to much snot in the back of my throat. My comedowns started to get worse. I would get depressed and paranoid. The only time I was happy was when I was doing coke or thinking about it. I disassociated myself with a lot of people. A few of my friends stopped before they got to this stage, and a few were right along side with me. My parents got my bank statement and flipped. I couldn't explain to them how I could spend a small fortune in the matter of two months.
I took a few breaks from my infatuation. Sometimes I'd go a whole week without blowing a line. It wasn't because I didn't want to do it, it was just because I ran out of funds. I took a step back and realized that in a matter of two months cocaine robbed a lot from me. It opened me up to an aspect of drugs I never knew before. I'm not going to say I was 'addicted', but I was damn sure loving every line I did. Luckily, before things got to out of control, I found the will to stop using. Well... cut down at least. I went back to doing it on weekends, sometimes every other weekend. That was a few months ago, and I've managed to keep my usage to every other weekend up until this date. I have a friend who is still deep into the game. He's a reck. He must have spent a good ten grand on his addiction. He's failing out of school, he lies, he steals, and he has no friends. He was a shell of the person he once was.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Our Bed and Breakfast is located in a typical Venetian area, on the second floor of a Venetian palace,
with private entrance and canal view, close to San Marco Square.
The neighbourhood is very beautiful and characteristic, the house is just a footstep away from the most important monuments, churches and shops,
with restaurants, pizzerias and bars around the corner.
Take a look at our comfortable and elegant rooms. Each bedroom has a seating area and balcony overlooking the canal.


name repeat
name required
name length should be longer then 4
name length should be shorter then 10
email required
email is illegal
password is required


person_pin
PSU Passpost
Welcome to PSU Passpost
contacts
User Name
vpn_key
Password
play_arrow
SIGN IN


Error - This tool is supported only on App running on Dedicated SKU's (Basic,
Standard, Isolated, Premium and PremiumV2)
Error - It appears that you do not have permissions on the App Service Plan. This
happens typically if you have Website Contributor access only and no permissions on the App Service
Plan
Error - {{ errorMessage }}


Lists and Links
In this assignment, I created a folder called "listsandlinks". I Added a html and a css file to the folder. I made a website page with the listsandlinks folder. This assignment taught me how to create an ordered and a unordered list in html and add links to your website.
Tables
In this assignment, I created a folder called "tables". I Added a html and a css file to the folder. I made a website page with the tables folder. This assignment taught me how to create an tables including a simple grid, a calender, and a class scedule. I also learned how to add a link to websites.
This website will contain projects completed for the Web Design part of Computer Science 1 at CMIS


{{page.banner-title}}
{{page.banner-content}}
I am absolutely in love with technology, and I firmly believe that good design is an integral part of a solid product. With this belief in mind, I have directed my attention to usability, human-computer interaction, and front-end development. I am a software engineer at heart; however, so I understand the underlying implementation of a website or application is just as important as making the UI aesthetically pleasing.
Check out the other pages to find out more about who I am and what I do. I'm always searching for new opportunites and interesting people with whom to network, so please email me or contact me on any of the social networks linked below.
Check Out My Resume
While I'm not actively looking for a job, you can take a look at my resume to see if I'm the one you're looking for at your company!
Current Projects
I'm currently a Software Engineer at Vista Higher Learning. Outside of work, I'm focused on building a healthy, sustainable lifestyle and learning new things daily.


Family of cockroaches found living inside man's ear after he felt sharp pain
WARNING - GRAPHIC CONTENT: The mother parasite laid over a dozen eggs inside him before doctors came to the rescue in South China's Guangdong Province
by Sam Elliott, John Feng, https://www.mirror.co.uk/authors/sam-elliott/This is the disturbing moment shocked doctors discovered a family of tiny cockroaches living inside a man's ear.
Unsuspecting Mr Lv, 24, wanted to get to the bottom of his head problem at Sanhe Hospital in Huiyang, South China.
He said he felt a sharp pain in his right ear while sleeping so his family members shone a torch into his ear canal. They found what appeared to be a large cockroach inside.
 It caused a lot of discomfort.
"I discovered more than ten cockroach babies inside. They were already running around."
The newly hatched nymphs, which were small and lighter in colour than their black and brown mother, were of the German cockroach species Blattella germanica, the hospital said.
Doctor Zhong plucked the tiny insects from Mr Lv's right ear one by one using a pair of tweezers, before also removing the much larger mother roach.
According to the hospital, Mr Lv suffered minor injuries to his right ear canal. He was prescribed with ointment and cream, and discharged on the same day.
The hospital's head of ENT, Li Jinyuan, told local media that Mr Lv had a habit of leaving unfinished food packets near his bed, attracting parasites such as cockRoaches.
Female cockroaches carry up to 40 eggs, reports say.
Deputy head of ENT Jiang Tengxiang advised: "Household hygiene helps to prevent the appearance and spread of cockroaches.
"Disinfect drains and sewers. Use mosquito nets and screens on windows.
"That'll stop insects from flying or crawling into your noses and ears."


u-root is an embeddable root file system intended to be placed in a flash device as part of the firmware image, along with a Linux kernel. Unlike most embedded root file systems, which consist of large binaries, u-root only has five: an init program and four Go compiler binaries.

More instructions can be found in the repo’s README.md.
We use GitHub Pull Requests for code review. Pull requests must receive one approval and pass CI before being merged.
It’s to reflect a universal root, you can mount on every local and get a userland portable (it’s a goal).
The Go gopher was designed by Renee French. The u-root logo design is licensed under the Creative Commons 3.0 Attributions license.
The logo is communicating several things:
u-root has several flavors: firmware and as a root file system
the gopher at the bottom is a firmware u-root; that gopher brings the machine up, hence the wrench. Its work is also done, so it is resting.
the other gophers can make more copies of u-root; hence the u-root logo on their chest.
the highest gopher is showing how u-root is a good root file system for a VM.
the U itself is a stylized tree, evocative of roots.


Saracen to buy Barrick's share of Australian super-pit for US$750M
by Jim SilverBarrick Gold said it agreed to sell its 50 per cent stake in Kalgoorlie Consolidated Gold Mines in Western Australia to Saracen Mineral Holdings for US$750 millon in cash.
More coming


Cyclotron - a jQuery plugin to display cylindrical panorama images
Code of this Cyclotron fork is available at
https://github.com/quelbs/cyclotron
.
Panorama moveable with mouse and touch events
.cyclotron();
Panorama with autorotate and no damping of movement
.cyclotron({dampingFactor:1,autorotation:1});
non-continuous panorama
.cyclotron({continuous:0});
non-continuous panorama autorotate
.cyclotron({continuous:0,dampingFactor:1,autorotation:1});


|
|
Owl Monitoring SystemSensor Installation Manual |
From time to time, you might decide to change the queries being performed by the Owl sensors. This could be adding new queries to some or all of the sensors, stopping some of the queries from being performed, or modifying existing queries. Regardless of the changes, there are actions that must be taken on the Owl manager and all affected Owl sensors.
It is relatively painless to modify queries for a sensor. The following actions must be performed:
If you have correctly set up your configuration file, then owl-dnstimer will start collecting data for the new queries.
Stopping collection of certain queries only requires deleting (or commenting out) the appropriate entries from the configuration file. owl-dnstimer, of course, must be restarted.
|
Section 4. Adding Sensors |
Owl Monitoring System Sensor Installation Manual |
Section 6. Owl Sensor Commands |


Hi, my name is Ben Ropple. I'm a recent graduate of the University of Maine in Orono, ME. I graduated with a Bachelor of Science degree in Electrical Engineering.
The projects I've worked on, my skill-set, and various links are all listed on my portfolio page. My full resume is available on my LinkedIn profile.
I am looking to begin my professional career in Electrical Engineering, predominantly in the power and embedded systems fields. Feel free to contact me via e-mail or LinkedIn.
This site also serves as my blog, where I will post short, informal write-ups of the projects I work on in my free time. These projects are listed below as they are posted!


This plug in shows the map rotation of each server as small map icons on the server browser. A must-have plugin for battlelog! This is the most used plugin of BBlog!
☰ Preview :
Features
- Show maps in rotation on servers
- Map rotation slideshow on click
- Map name & mode as tooltip
- Style same as the avatars
- Blue style on current map
- Works on BF3, BF4 & BFH
Images
Server Browser
(BF3 / BF4 / BFH)
Server Browser Popup Modal
(BF3 / BF4 / BFH)
☰ Nerd Stuff :
Changelog
v 1.7
(27.06.2016)
- BFH support added
v 1.6
(04.09.2015)
- CPU overload bug found and fixed
v 1.5
(26.9.2014)
- Style fixes (on style errors caused by bblog v4.5)
v 1.4
(12.09.2014)
- Several fixes pointed out by BrainFooLong (http://getbblog.com/en/board/post/126815)
- Quality code fixes
- Added minified version of the script
v 1.3
(07.09.2014)
- Rewrited bblog import code
- Also works on favourites & history
- CSS optimizations
- Added BF3 support
- Fixed chat bug
v 1.2
(06.09.2014)
- Map rotation slideshow on image click
- BF3: current map cannot always be specified (BF3 set as current every map based on title, so if you play metro, and the map rotations is 3 metro all are set as current)
☰ PlugIn Links :
(The plugin is also available in the PlugIn Gallery. You are adviced to load it from the Gallery.)
(
Please delete it from your plugins, and install it from the one-click button.
Then check again.
If it still don't work please report me your browser (name - version) and sent me a message with the console report (on your browser : F12 -> Console )
**EDIT**
One-click button no longer exist. Please use bblog's plug-in gallery to install it.

My web browser is Chrome(37.0.2062.103 m)
These methods are not work for me.
1. delete and re-install by one-click button
2. no chat
Console
Post edited 1 x times, last by
GreatApo
Topicstarter
GreatApo
I don't see any error from my script BUT there are some errors from other Chrome addons you have install. Try this, disable all your chrome addons exept from BBLog and try again...
If this works, one of your addons is messing with battlelog's code.
RamboDC
awesome, though it does not show up on favorites. with that it would be perfect.
Post edited 1 x times, last by
DarkThanos
DarkThanos
We are working on it.
Edit : Support added on version 1.3
Krayziesoldier
nice plugin, good job!
Post edited 4 x times, last by
BrainFooLong
Administrator
BrainFooLong
Administrator
This plugin contains a lot of bugs that make it in most cases unusable.
Bugs i've found
* Only work on native english pages (http://battlelog.battlefield.com/bf4/server..), pages with the language in the url doesn't work (http://battlelog.battlefield.com/bf4/de/server...)
* There are much unitialized variables which is not allowed in strict javascript code. for(page in ...)
must be
for(var page in ...)
Before you use a variable the first time you need to initliaze it with var myvar = ...
* instance.checkIf.loggedIn() is not required - BBLog only will be initialized when the user is already logged in.
* To check in which mode the page is you just need this BBLog.cache("mode") // return bf4,bf3,mohw,bfh
I recommend to inactivate the plugin in the plugin gallery and work on fixes.
Plugins in plugin gallery should only be well tested.
I tested in chrome and i tried several changes in the code to make it working, but everytime a new error appears.
Post edited 2 x times, last by
GreatApo
Topicstarter
GreatApo
Thanks for the feedback! We will fix these :D
CartmaniLP
nice work dude! :D
Topicstarter
GreatApo
BrainFooLong, i believe everything is fixed. Check it out...
I am waiting for your approval to enable it on the Plugin Gallery.
BrainFooLong
Administrator
Works in chrome without errors in my test.
Topicstarter
GreatApo
Me and Darkthanos created this plugin because we felt like this was a necessary feature that battlelog lucks... Now, i just can't choose a server without it...
I can see that there are 700 users per day using this addon... maybe it should be in BetterBattleLog's main code or default on?
@ BrainFooLong: I talked to DarkThanos and we agreed that if you want to implement it in BBLog (and improve it) you should go ahead.
BrainFooLong
Administrator
It's a good plugin and it's better to let it as a plugin.
Simply because there is a lot of work in this plugin and you deserve it that it is the most used plugin.
To integrate it into bblog this will cost me a lot of time, the code of the plugin is 20% of the whole bblog code :)
I don't have much time for bblog since a year or so, therefore i created the plugin and theme system to keep bblog active even if i have less time.
Greetz
Topicstarter
GreatApo
Even with your narrow time limits, you manage to keep BBLog alive... thats hard and everybody knows it :)


% include com/stdhead.html %>
<% include com/nav.html %>
<% if (verified) { %>
Welcome!
Your email is verified and your account is now active.
<% } %>
Activity
<% include com/activity.html %>
<% if (session) { %>
<%= userRecord.username %>
<% if (userRecord.archives.length > 0) { %> <% userRecord.archives.forEach(a => { %>
<%= a.name || a.key %>
<% }) %>
<% } else { %>
You have no sites uploaded.
<% } %>
New Site
<% } else { %> <% include com/home-cta.html %> <% } %>
<% include com/footer.html %> <% include com/stdjs.html %>


Explain a situation where you have had an ethical decision to make. Discuss how you weighed up the values
involved in that decision, the decision you made and the consequences of the action you took.
- Back at school, there were so many incidents where people would disrespect the vulnerable ones in the class, mostly girls who were too
afraid to speak up for themselves. There was one time when nobody stood up for this one girl because the guy was very 'popular' and I didn't even
have to think before supporting her! Looking back, I remember standing up and supporting people I didn't even know very well
if I saw them being bullied in class. I was afraid to be disliked by everyone cause it's scary to mess with people who have power, but
sometimes you have to draw a line!
Describe how your culture has influenced your values and identity.
- I'm a daughter of a desi rebellious mother who didn't/ still doesn't follow societies expectections, broke generations of trauma and is kind to everyone who crosses
her path- let me tell you, growing up watching that is mind blowing. It helped lay out a path for the kind of person I want to be. It solidified that
working hard for what you desire pays off. Kindness pays off. Giving back pays off.
Using the evidence gathered, describe your strengths and limitations.
- In the right environment I am very focussed, work extremely hard and achieve anything I set my mind to. I can
make learning fun for myself and everyone around me.
However, I get restless with a lot of reading or when . I've come to understand that I don't always understand the
generic logical analogies. I need an emotional example to understand concepts.
Evaluate your strengths and limitations in terms of your learning and career development
- I think my EQ is my strength, I have a vision of where I'd like to be and I work towards it. Slowly, but steadily and I get there.
However, my confidence when I don't get something right after trying a few times, is my weakness. I want to have more self confidence and
be content with self-validation.
Identify which of your strengths might help you in your learning journey and how they might intersect with
learning obstacles.
- I beleive my focus when I am interested in something and my determination once I am invested in a project, I become unstoppable. I also
think I am aware when I am losing interest when something gets tough and I take time away to do other activities/ recharge,
Focus, self awareness and determination will help me when I am faced with obstacles.
Share an example from your experience of where you were trying to work productively with others, but there was
resistance or tension. Discuss the strategies you used at that time, how effective they were, and your
reflections on what other strategies you would try now, and why.
- In my latest job, there was always conflict when ideas clashed and in our ways of communication. I always took a step back in these situations
and was able to talk to the person in a way they would understand. Sometimes it was very challenging, but taking time away, reflecting and creating good
boundaries really helped!


About this Document
This document describes changes between SQLAlchemy version 0.6, last released May 5, 2012, and SQLAlchemy version 0.7, undergoing maintenance releases as of October, 2012.
Document date: July 27, 2011
This guide introduces what’s new in SQLAlchemy version 0.7, and also documents changes which affect users migrating their applications from the 0.6 series of SQLAlchemy to 0.7.
To as great a degree as possible, changes are made in such a way as to not break compatibility with applications built for 0.6. The changes that are necessarily not backwards compatible are very few, and all but one, the change to mutable attribute defaults, should affect an exceedingly small portion of applications - many of the changes regard non-public APIs and undocumented hacks some users may have been attempting to use.
A second, even smaller class of non-backwards-compatible changes is also documented. This class of change regards those features and behaviors that have been deprecated at least since version 0.5 and have been raising warnings since their deprecation. These changes would only affect applications that are still using 0.4- or early 0.5-style APIs. As the project matures, we have fewer and fewer of these kinds of changes with 0.x level releases, which is a product of our API having ever fewer features that are less than ideal for the use cases they were meant to solve.
An array of existing functionalities have been superseded in SQLAlchemy 0.7. There’s not much difference between the terms “superseded” and “deprecated”, except that the former has a much weaker suggestion of the old feature would ever be removed. In 0.7, features like synonym and comparable_property, as well as all the Extension and other event classes, have been superseded. But these “superseded” features have been re-implemented such that their implementations live mostly outside of core ORM code, so their continued “hanging around” doesn’t impact SQLAlchemy’s ability to further streamline and refine its internals, and we expect them to remain within the API for the foreseeable future.
SQLAlchemy started early with the MapperExtension class, which provided hooks into the persistence cycle of mappers. As SQLAlchemy quickly became more componentized, pushing mappers into a more focused configurational role, many more “extension”, “listener”, and “proxy” classes popped up to solve various activity-interception use cases in an ad-hoc fashion. Part of this was driven by the divergence of activities; ConnectionProxy objects wanted to provide a system of rewriting statements and parameters; AttributeExtension provided a system of replacing incoming values, and DDL objects had events that could be switched off of dialect-sensitive callables.
0.7 re-implements virtually all of these plugin points with a new, unified approach, which retains all the functionalities of the different systems, provides more flexibility and less boilerplate, performs better, and eliminates the need to learn radically different APIs for each event subsystem. The pre-existing classes MapperExtension, SessionExtension, AttributeExtension, ConnectionProxy, PoolListener as well as the DDLElement.execute_at method are deprecated and now implemented in terms of the new system - these APIs remain fully functional and are expected to remain in place for the foreseeable future.
The new approach uses named events and user-defined callables to associate activities with events. The API’s look and feel was driven by such diverse sources as JQuery, Blinker, and Hibernate, and was also modified further on several occasions during conferences with dozens of users on Twitter, which appears to have a much higher response rate than the mailing list for such questions.
It also features an open-ended system of target specification that allows events to be associated with API classes, such as for all Session or Engine objects, with specific instances of API classes, such as for a specific Pool or Mapper, as well as for related objects like a user- defined class that’s mapped, or something as specific as a certain attribute on instances of a particular subclass of a mapped parent class. Individual listener subsystems can apply wrappers to incoming user- defined listener functions which modify how they are called - an mapper event can receive either the instance of the object being operated upon, or its underlying InstanceState object. An attribute event can opt whether or not to have the responsibility of returning a new value.
Several systems now build upon the new event API, including the new “mutable attributes” API as well as composite attributes. The greater emphasis on events has also led to the introduction of a handful of new events, including attribute expiration and refresh operations, pickle loads/dumps operations, completed mapper construction operations.
See also
The “derived attributes” example has now been turned into an official extension. The typical use case for synonym() is to provide descriptor access to a mapped column; the use case for comparable_property() is to be able to return a PropComparator from any descriptor. In practice, the approach of “derived” is easier to use, more extensible, is implemented in a few dozen lines of pure Python with almost no imports, and doesn’t require the ORM core to even be aware of it. The feature is now known as the “Hybrid Attributes” extension.
synonym() and comparable_property() are still part of the ORM, though their implementations have been moved outwards, building on an approach that is similar to that of the hybrid extension, so that the core ORM mapper/query/property modules aren’t really aware of them otherwise.
See also
As is customary with all major SQLA releases, a wide pass through the internals to reduce overhead and callcounts has been made which further reduces the work needed in common scenarios. Highlights of this release include:
A demonstration of callcount reduction including a sample benchmark script is at http://techspot.zzzeek.org/2010/12/12/a-tale-of-three- profiles/
The “composite” feature has been rewritten, like synonym() and comparable_property(), to use a lighter weight implementation based on descriptors and events, rather than building into the ORM internals. This allowed the removal of some latency from the mapper/unit of work internals, and simplifies the workings of composite. The composite attribute now no longer conceals the underlying columns it builds upon, which now remain as regular attributes. Composites can also act as a proxy for relationship() as well as Column() attributes.
The major backwards-incompatible change of composites is that they no longer use the mutable=True system to detect in-place mutations. Please use the Mutation Tracking extension to establish in-place change events to existing composite usage.
The default method of issuing query.join() to a target with an explicit onclause is now:
query.join(SomeClass, SomeClass.id==ParentClass.some_id)
In 0.6, this usage was considered to be an error, because join() accepts multiple arguments corresponding to multiple JOIN clauses - the two-argument form needed to be in a tuple to disambiguate between single-argument and two- argument join targets. In the middle of 0.6 we added detection and an error message for this specific calling style, since it was so common. In 0.7, since we are detecting the exact pattern anyway, and since having to type out a tuple for no reason is extremely annoying, the non- tuple method now becomes the “normal” way to do it. The “multiple JOIN” use case is exceedingly rare compared to the single join case, and multiple joins these days are more clearly represented by multiple calls to join().
The tuple form will remain for backwards compatibility.
Note that all the other forms of query.join() remain unchanged:
query.join(MyClass.somerelation)
query.join("somerelation")
query.join(MyTarget)
# ... etc
A new extension, Mutation Tracking, provides a mechanism by which user-defined datatypes can provide change events back to the owning parent or parents. The extension includes an approach for scalar database values, such as those managed by PickleType, postgresql.ARRAY, or other custom MutableType classes, as well as an approach for ORM “composites”, those configured using :ref:`composite() <mapper_composite>`_.
See also
These are implemented as an extension to the asc() and desc() operators, called nullsfirst() and nullslast().
This was already available by passing a list of expressions to the distinct keyword argument of select(), the distinct() method of select() and Query now accept positional arguments which are rendered as DISTINCT ON when a Postgresql backend is used.
The Index() construct can be created inline with a Table definition, using strings as column names, as an alternative to the creation of the index outside of the Table. That is:
Table('mytable', metadata,
Column('id',Integer, primary_key=True),
Column('name', String(50), nullable=False),
Index('idx_name', 'name')
)
The primary rationale here is for the benefit of declarative __table_args__, particularly when used with mixins:
class HasNameMixin(object):
name = Column('name', String(50), nullable=False)
@declared_attr
def __table_args__(cls):
return (Index('name'), {})
class User(HasNameMixin, Base):
__tablename__ = 'user'
id = Column('id', Integer, primary_key=True)
A “window function” provides to a statement information about the result set as it’s produced. This allows criteria against various things like “row number”, “rank” and so forth. They are known to be supported at least by Postgresql, SQL Server and Oracle, possibly others.
The best introduction to window functions is on Postgresql’s site, where window functions have been supported since version 8.4:
http://www.postgresql.org/docs/9.0/static/tutorial- window.html
SQLAlchemy provides a simple construct typically invoked via an existing function clause, using the over() method, which accepts order_by and partition_by keyword arguments. Below we replicate the first example in PG’s tutorial:
from sqlalchemy.sql import table, column, select, func
empsalary = table('empsalary',
column('depname'),
column('empno'),
column('salary'))
s = select([
empsalary,
func.avg(empsalary.c.salary).
over(partition_by=empsalary.c.depname).
label('avg')
])
print s
SQL:
SELECT empsalary.depname, empsalary.empno, empsalary.salary,
avg(empsalary.salary) OVER (PARTITION BY empsalary.depname) AS avg
FROM empsalary
This sets the transaction isolation level for a single Connection, until that Connection is closed and its underlying DBAPI resource returned to the connection pool, upon which the isolation level is reset back to the default. The default isolation level is set using the isolation_level argument to create_engine().
Transaction isolation support is currently only supported by the Postgresql and SQLite backends.
A TypeDecorator which extends the behavior of Integer can be used with a primary key column. The “autoincrement” feature of Column will now recognize that the underlying database column is still an integer so that lastrowid mechanisms continue to function. The TypeDecorator itself will have its result value processor applied to newly generated primary keys, including those received by the DBAPI cursor.lastrowid accessor.
No longer need to import this from sqlalchemy.types, it’s now mirrored in sqlalchemy.
Dialects have been added:
a MySQLdb driver for the Drizzle database:
support for the pymysql DBAPI:
psycopg2 now works with Python 3
This is as of 0.7b4. The exts will build if cPython 2.xx is detected. If the build fails, such as on a windows install, that condition is caught and the non-C install proceeds. The C exts won’t build if Python 3 or Pypy is used.
The very old guesswork which occurred within Query.count() has been modernized to use .from_self(). That is, query.count() is now equivalent to:
query.from_self(func.count(literal_column('1'))).scalar()
Previously, internal logic attempted to rewrite the columns clause of the query itself, and upon detection of a “subquery” condition, such as a column-based query that might have aggregates in it, or a query with DISTINCT, would go through a convoluted process of rewriting the columns clause. This logic failed in complex conditions, particularly those involving joined table inheritance, and was long obsolete by the more comprehensive .from_self() call.
The SQL emitted by query.count() is now always of the form:
SELECT count(1) AS count_1 FROM (
SELECT user.id AS user_id, user.name AS user_name from user
) AS anon_1
that is, the original query is preserved entirely inside of a subquery, with no more guessing as to how count should be applied.
MySQL users have already reported that the MyISAM engine not surprisingly falls over completely with this simple change. Note that for a simple count() that optimizes for DBs that can’t handle simple subqueries, func.count() should be used:
from sqlalchemy import func
session.query(func.count(MyClass.id)).scalar()
or for count(*):
from sqlalchemy import func, literal_column
session.query(func.count(literal_column('*'))).select_from(MyClass).scalar()
The LIMIT and OFFSET clauses, or their backend equivalents (i.e. TOP, ROW NUMBER OVER, etc.), use bind parameters for the actual values, for all backends which support it (most except for Sybase). This allows better query optimizer performance as the textual string for multiple statements with differing LIMIT/OFFSET are now identical.
Vinay Sajip has provided a patch to our logging system such that the “hex string” embedded in logging statements for engines and pools is no longer needed to allow the echo flag to work correctly. A new system that uses filtered logging objects allows us to maintain our current behavior of echo being local to individual engines without the need for additional identifying strings local to those engines.
The population of the polymorphic_on column-mapped attribute, when used in an inheritance scenario, now occurs when the object is constructed, i.e. its __init__ method is called, using the init event. The attribute then behaves the same as any other column-mapped attribute. Previously, special logic would fire off during flush to populate this column, which prevented any user code from modifying its behavior. The new approach improves upon this in three ways: 1. the polymorphic identity is now present on the object as soon as its constructed; 2. the polymorphic identity can be changed by user code without any difference in behavior from any other column-mapped attribute; 3. the internals of the mapper during flush are simplified and no longer need to make special checks for this column.
The `contains_eager()`` modifier now will chain itself for a longer path without the need to emit individual ``contains_eager()` calls. Instead of:
session.query(A).options(contains_eager(A.b), contains_eager(A.b, B.c))
you can say:
session.query(A).options(contains_eager(A.b, B.c))
We’ve had a long standing behavior that checks for a so- called “orphan” during flush, that is, an object which is associated with a relationship() that specifies “delete- orphan” cascade, has been newly added to the session for an INSERT, and no parent relationship has been established. This check was added years ago to accommodate some test cases which tested the orphan behavior for consistency. In modern SQLA, this check is no longer needed on the Python side. The equivalent behavior of the “orphan check” is accomplished by making the foreign key reference to the object’s parent row NOT NULL, where the database does its job of establishing data consistency in the same way SQLA allows most other operations to do. If the object’s parent foreign key is nullable, then the row can be inserted. The “orphan” behavior runs when the object was persisted with a particular parent, and is then disassociated with that parent, leading to a DELETE statement emitted for it.
Warnings are now emitted when related objects referenced via a loaded relationship() on a parent object marked as “dirty” are not present in the current Session.
The save-update cascade takes effect when objects are added to the Session, or when objects are first associated with a parent, so that an object and everything related to it are usually all present in the same Session. However, if save-update cascade is disabled for a particular relationship(), then this behavior does not occur, and the flush process does not try to correct for it, instead staying consistent to the configured cascade behavior. Previously, when such objects were detected during the flush, they were silently skipped. The new behavior is that a warning is emitted, for the purposes of alerting to a situation that more often than not is the source of unexpected behavior.
Since we moved to nose we’ve used a plugin that installs via setuptools, so that the nosetests script would automatically run SQLA’s plugin code, necessary for our tests to have a full environment. In the middle of 0.6, we realized that the import pattern here meant that Nose’s “coverage” plugin would break, since “coverage” requires that it be started before any modules to be covered are imported; so in the middle of 0.6 we made the situation worse by adding a separate sqlalchemy-nose package to the build to overcome this.
In 0.7 we’ve done away with trying to get nosetests to work automatically, since the SQLAlchemy module would produce a large number of nose configuration options for all usages of nosetests, not just the SQLAlchemy unit tests themselves, and the additional sqlalchemy-nose install was an even worse idea, producing an extra package in Python environments. The sqla_nose.py script in 0.7 is now the only way to run the tests with nose.
A construct that isn’t against any Table at all, like a function, can be mapped.
from sqlalchemy import select, func
from sqlalchemy.orm import mapper
class Subset(object):
pass
selectable = select(["x", "y", "z"]).select_from(func.some_db_function()).alias()
mapper(Subset, selectable, primary_key=[selectable.c.x])
This is a convenience helper such that in the case a plain FromClause, such as a select, Table or join is passed to the orm.aliased() construct, it passes through to the .alias() method of that from construct rather than constructing an ORM level AliasedClass.
This is to allow execute/connection operations to participate in the open transaction of an engine explicitly. It also allows custom subclasses of Session that implement their own get_bind() method and arguments to use those custom arguments with both the execute() and connection() methods equally.
Bind parameters present in the “columns clause” of a select are now auto-labeled like other “anonymous” clauses, which among other things allows their “type” to be meaningful when the row is fetched, as in result row processors.
This so that a script that changes the current directory will continue to target the same location as subsequent SQLite connections are established.
On the MS-SQL backend, the String/Unicode types, and their counterparts VARCHAR/ NVARCHAR, as well as VARBINARY (#1833) emit “max” as the length when no length is specified. This makes it more compatible with Postgresql’s VARCHAR type which is similarly unbounded when no length specified. SQL Server defaults the length on these types to ‘1’ when no length is specified.
Note again, aside from the default mutability change, most of these changes are *extremely minor* and will not affect most users.
This change refers to the default behavior of the ORM when mapping columns that have either the PickleType or postgresql.ARRAY datatypes. The mutable flag is now set to False by default. If an existing application uses these types and depends upon detection of in-place mutations, the type object must be constructed with mutable=True to restore the 0.6 behavior:
Table('mytable', metadata,
# ....
Column('pickled_data', PickleType(mutable=True))
)
The mutable=True flag is being phased out, in favor of the new Mutation Tracking extension. This extension provides a mechanism by which user-defined datatypes can provide change events back to the owning parent or parents.
The previous approach of using mutable=True does not provide for change events - instead, the ORM must scan through all mutable values present in a session and compare them against their original value for changes every time flush() is called, which is a very time consuming event. This is a holdover from the very early days of SQLAlchemy when flush() was not automatic and the history tracking system was not nearly as sophisticated as it is now.
Existing applications which use PickleType, postgresql.ARRAY or other MutableType subclasses, and require in-place mutation detection, should migrate to the new mutation tracking system, as mutable=True is likely to be deprecated in the future.
So-called “composite” mapped attributes, those configured using the technique described at Composite Column Types, have been re-implemented such that the ORM internals are no longer aware of them (leading to shorter and more efficient codepaths in critical sections). While composite types are generally intended to be treated as immutable value objects, this was never enforced. For applications that use composites with mutability, the Mutation Tracking extension offers a base class which establishes a mechanism for user-defined composite types to send change event messages back to the owning parent or parents of each object.
Applications which use composite types and rely upon in- place mutation detection of these objects should either migrate to the “mutation tracking” extension, or change the usage of the composite types such that in-place changes are no longer needed (i.e., treat them as immutable value objects).
This change is 99.999% backwards compatible, unless you are using temporary tables across connection pool connections.
A file-based SQLite connection is blazingly fast, and using NullPool means that each call to Engine.connect creates a new pysqlite connection.
Previously, the SingletonThreadPool was used, which meant that all connections to a certain engine in a thread would be the same connection. It’s intended that the new approach is more intuitive, particularly when multiple connections are used.
SingletonThreadPool is still the default engine when a :memory: database is used.
Note that this change breaks temporary tables used across Session commits, due to the way SQLite handles temp tables. See the note at http://www.sqlalchemy.org/docs/dialects/sqlite.html#using- temporary-tables-with-sqlite if temporary tables beyond the scope of one pool connection are desired.
Session.merge() will check the version id of the incoming state against that of the database, assuming the mapping uses version ids and incoming state has a version_id assigned, and raise StaleDataError if they don’t match. This is the correct behavior, in that if incoming state contains a stale version id, it should be assumed the state is stale.
If merging data into a versioned state, the version id attribute can be left undefined, and no version check will take place.
This check was confirmed by examining what Hibernate does - both the merge() and the versioning features were originally adapted from Hibernate.
This improvement is potentially slightly backwards incompatible for an application that relied upon the old behavior.
Given two mapped classes Foo and Bar each with a column spam:
qa = session.query(Foo.spam)
qb = session.query(Bar.spam)
qu = qa.union(qb)
The name given to the single column yielded by qu will be spam. Previously it would be something like foo_spam due to the way the union would combine things, which is inconsistent with the name spam in the case of a non-unioned query.
This is a change to the behavior involved when a mapped column attribute references multiple columns, specifically when dealing with an attribute on a joined-table subclass that has the same name as that of an attribute on the superclass.
Using declarative, the scenario is this:
class Parent(Base):
__tablename__ = 'parent'
id = Column(Integer, primary_key=True)
class Child(Parent):
__tablename__ = 'child'
id = Column(Integer, ForeignKey('parent.id'), primary_key=True)
Above, the attribute Child.id refers to both the child.id column as well as parent.id - this due to the name of the attribute. If it were named differently on the class, such as Child.child_id, it then maps distinctly to child.id, with Child.id being the same attribute as Parent.id.
When the id attribute is made to reference both parent.id and child.id, it stores them in an ordered list. An expression such as Child.id then refers to just one of those columns when rendered. Up until 0.6, this column would be parent.id. In 0.7, it is the less surprising child.id.
The legacy of this behavior deals with behaviors and restrictions of the ORM that don’t really apply anymore; all that was needed was to reverse the order.
A primary advantage of this approach is that it’s now easier to construct primaryjoin expressions that refer to the local column:
class Child(Parent):
__tablename__ = 'child'
id = Column(Integer, ForeignKey('parent.id'), primary_key=True)
some_related = relationship("SomeRelated",
primaryjoin="Child.id==SomeRelated.child_id")
class SomeRelated(Base):
__tablename__ = 'some_related'
id = Column(Integer, primary_key=True)
child_id = Column(Integer, ForeignKey('child.id'))
Prior to 0.7 the Child.id expression would reference Parent.id, and it would be necessary to map child.id to a distinct attribute.
It also means that a query like this one changes its behavior:
session.query(Parent).filter(Child.id > 7)
In 0.6, this would render:
SELECT parent.id AS parent_id
FROM parent
WHERE parent.id > :id_1
in 0.7, you get:
SELECT parent.id AS parent_id
FROM parent, child
WHERE child.id > :id_1
which you’ll note is a cartesian product - this behavior is now equivalent to that of any other attribute that is local to Child. The with_polymorphic() method, or a similar strategy of explicitly joining the underlying Table objects, is used to render a query against all Parent objects with criteria against Child, in the same manner as that of 0.5 and 0.6:
print s.query(Parent).with_polymorphic([Child]).filter(Child.id > 7)
Which on both 0.6 and 0.7 renders:
SELECT parent.id AS parent_id, child.id AS child_id
FROM parent LEFT OUTER JOIN child ON parent.id = child.id
WHERE child.id > :id_1
Another effect of this change is that a joined-inheritance load across two tables will populate from the child table’s value, not that of the parent table. An unusual case is that a query against “Parent” using with_polymorphic="*" issues a query against “parent”, with a LEFT OUTER JOIN to “child”. The row is located in “Parent”, sees the polymorphic identity corresponds to “Child”, but suppose the actual row in “child” has been deleted. Due to this corruption, the row comes in with all the columns corresponding to “child” set to NULL - this is now the value that gets populated, not the one in the parent table.
This is somewhat related to the previous change in #1892. When mapping to a join, same-named columns must be explicitly linked to mapped attributes, i.e. as described in Mapping a Class Against Multiple Tables.
Given two tables foo and bar, each with a primary key column id, the following now produces an error:
foobar = foo.join(bar, foo.c.id==bar.c.foo_id)
mapper(FooBar, foobar)
This because the mapper() refuses to guess what column is the primary representation of FooBar.id - is it foo.c.id or is it bar.c.id ? The attribute must be explicit:
foobar = foo.join(bar, foo.c.id==bar.c.foo_id)
mapper(FooBar, foobar, properties={
'id':[foo.c.id, bar.c.id]
})
This is a warning in 0.6, now an error in 0.7. The column given for polymorphic_on must be in the mapped selectable. This to prevent some occasional user errors such as:
mapper(SomeClass, sometable, polymorphic_on=some_lookup_table.c.id)
where above the polymorphic_on needs to be on a sometable column, in this case perhaps sometable.c.some_lookup_id. There are also some “polymorphic union” scenarios where similar mistakes sometimes occur.
Such a configuration error has always been “wrong”, and the above mapping doesn’t work as specified - the column would be ignored. It is however potentially backwards incompatible in the rare case that an application has been unknowingly relying upon this behavior.
Previously, percent signs in DDL() strings would have to be escaped, i.e. %% depending on DBAPI, for those DBAPIs that accept pyformat or format binds (i.e. psycopg2, mysql-python), which was inconsistent versus text() constructs which did this automatically. The same escaping now occurs for DDL() as for text().
Another area where some users were tinkering around in such a way that doesn’t actually work as expected, but still left an exceedingly small chance that some application was relying upon this behavior, the construct returned by the .c attribute on Table and the .tables attribute on MetaData is explicitly non-mutable. The “mutable” version of the construct is now private. Adding columns to .c involves using the append_column() method of Table, which ensures things are associated with the parent Table in the appropriate way; similarly, MetaData.tables has a contract with the Table objects stored in this dictionary, as well as a little bit of new bookkeeping in that a set() of all schema names is tracked, which is satisfied only by using the public Table constructor as well as Table.tometadata().
It is of course possible that the ColumnCollection and dict collections consulted by these attributes could someday implement events on all of their mutational methods such that the appropriate bookkeeping occurred upon direct mutation of the collections, but until someone has the motivation to implement all that along with dozens of new unit tests, narrowing the paths to mutation of these collections will ensure no application is attempting to rely upon usages that are currently not supported.
Established consistency when server_default is present on an Integer PK column. SQLA doesn’t pre-fetch these, nor do they come back in cursor.lastrowid (DBAPI). Ensured all backends consistently return None in result.inserted_primary_key for these - some backends may have returned a value previously. Using a server_default on a primary key column is extremely unusual. If a special function or SQL expression is used to generate primary key defaults, this should be established as a Python-side “default” instead of server_default.
Regarding reflection for this case, reflection of an int PK col with a server_default sets the “autoincrement” flag to False, except in the case of a PG SERIAL col where we detected a sequence default.
For a few years we’ve added the string sqlalchemy.exceptions to sys.modules, so that a statement like “import sqlalchemy.exceptions” would work. The name of the core exceptions module has been exc for a long time now, so the recommended import for this module is:
from sqlalchemy import exc
The exceptions name is still present in “sqlalchemy” for applications which might have said from sqlalchemy import exceptions, but they should also start using the exc name.
While not part of SQLAlchemy itself, it’s worth mentioning that the rework of the ConnectionProxy into the new event system means it is no longer appropriate for the “Timing all Queries” recipe. Please adjust query-timers to use the before_cursor_execute() and after_cursor_execute() events, demonstrated in the updated recipe UsageRecipes/Profiling.
Simple types like Integer, Date etc. in the core types module don’t accept arguments. The default constructor that accepts/ignores a catchall \*args, \**kwargs is restored as of 0.7b4/0.7.0, but emits a deprecation warning.
If arguments are being used with a core type like Integer, it may be that you intended to use a dialect specific type, such as sqlalchemy.dialects.mysql.INTEGER which does accept a “display_width” argument for example.
This system slowly morphed from something small, implemented local to an individual mapper, and poorly named into something that’s more of a global “registry-” level function and poorly named, so we’ve fixed both by moving the implementation out of Mapper altogether and renaming it to configure_mappers(). It is of course normally not needed for an application to call configure_mappers() as this process occurs on an as-needed basis, as soon as the mappings are needed via attribute or query access.
PoolListener, ConnectionProxy, DDLElement.execute_at are superseded by event.listen(), using the PoolEvents, EngineEvents, DDLEvents dispatch targets, respectively.
MapperExtension, AttributeExtension, SessionExtension are superseded by event.listen(), using the MapperEvents/InstanceEvents, AttributeEvents, SessionEvents, dispatch targets, respectively.
This obscure feature allows this pattern with the MySQL backend:
select([mytable], distinct='ALL', prefixes=['HIGH_PRIORITY'])
The prefixes keyword or prefix_with() method should be used for non-standard or unusual prefixes:
select([mytable]).prefix_with('HIGH_PRIORITY', 'ALL')
The useexisting flag on Table has been superseded by a new pair of flags keep_existing and extend_existing. extend_existing is equivalent to useexisting - the existing Table is returned, and additional constructor elements are added. With keep_existing, the existing Table is returned, but additional constructor elements are not added - these elements are only applied when the Table is newly created.
Note this affects the Beaker caching example, where the workings of the _params_from_query() function needed a slight adjustment. If you’re using code from the Beaker example, this change should be applied.
We noticed some users tapping into this dictionary inside of sqlalchemy.types as a shortcut to associating Python types with SQL types. We can’t guarantee the contents or format of this dictionary, and additionally the business of associating Python types in a one-to-one fashion has some grey areas that should are best decided by individual applications, so we’ve underscored this attribute.
This so that the keyword argument name matches that of the alias() methods on all FromClause objects as well as the name argument on Query.subquery().
Only code that uses the standalone alias() function, and not the method bound functions, and passes the alias name using the explicit keyword name alias, and not positionally, would need modification here.
All methods of Pool and subclasses which are not intended for public use have been renamed with underscores. That they were not named this way previously was a bug.
Pooling methods now underscored or removed:
Pool.create_connection() -> Pool._create_connection()
Pool.do_get() -> Pool._do_get()
Pool.do_return_conn() -> Pool._do_return_conn()
Pool.do_return_invalid() -> removed, was not used
Pool.return_conn() -> Pool._return_conn()
Pool.get() -> Pool._get(), public API is Pool.connect()
SingletonThreadPool.cleanup() -> _cleanup()
SingletonThreadPool.dispose_local() -> removed, use conn.invalidate()
Passing a list of attributes or attribute names to Query.join, eagerload(), and similar has been deprecated since 0.5:
# old way, deprecated since 0.5
session.query(Houses).join([Houses.rooms, Room.closets])
session.query(Houses).options(eagerload_all([Houses.rooms, Room.closets]))
These methods all accept *args as of the 0.5 series:
# current way, in place since 0.5
session.query(Houses).join(Houses.rooms, Room.closets)
session.query(Houses).options(eagerload_all(Houses.rooms, Room.closets))
This feature provided a mapper extension which linked class- based functionality with a particular ScopedSession, in particular providing the behavior such that new object instances would be automatically associated with that session. The feature was overused by tutorials and frameworks which led to great user confusion due to its implicit behavior, and was deprecated in 0.5.5. Techniques for replicating its functionality are at [wiki:UsageRecipes/SessionAwareMapper]


Contains page classes, and also the WebPage interface and its abstract implementation AbstractWebPage.
Also contains the top level dashboard pages.


1.20.1 / 2014-06-03
- update: should dependency to ~4.0.0 (#1231)
1.20.0 / 2014-05-28
- add: filenames to suite objects (#1222)
1.19.0 / 2014-05-17
- add: browser script option to package.json
- add: export file in Mocha.Test objects (#1174)
- add: add docs for wrapped node flags
- fix: mocha.run() to return error status in browser (#1216)
- fix: clean() to show failure details (#1205)
- fix: regex that generates html for new keyword (#1201)
- fix: sibling suites have inherited but separate contexts (#1164)
1.18.2 / 2014-03-18
- fix: html runner was prevented from using #mocha as the default root el (#1162)
1.18.1 / 2014-03-18
- fix: named before/after hooks in bdd, tdd, qunit interfaces (#1161)
1.18.0 / 2014-03-13
- add: promise support (#329)
- add: named before/after hooks (#966)
1.17.1 / 2014-01-22
- fix: expected messages in should.js (should.js#168)
- fix: expect errno global in node versions < v0.9.11 (#1111)
- fix: unreliable checkGlobals optimization (#1110)
1.17.0 / 2014-01-09
- add: able to require globals (describe, it, etc.) through mocha (#1077)
- fix: abort previous run on –watch change (#1100)
- fix: reset context for each –watch triggered run (#1099)
- fix: error when cli can’t resolve path or pattern (#799)
- fix: canonicalize objects before stringifying and diffing them (#1079)
- fix: make CR call behave like carriage return for non tty (#1087)
1.16.2 / 2013-12-23
- fix: couple issues with ie 8 (#1082, #1081)
- fix: issue running the xunit reporter in browsers (#1068)
- fix: issue with firefox < 3.5 (#725)
1.16.1 / 2013-12-19
- fix: recompiled for missed changes from the last release
1.16.0 / 2013-12-19
- add: Runnable.globals(arr) for per test global whitelist (#1046)
- add: mocha.throwError(err) for assertion libs to call (#985)
- remove: –watch’s spinner (#806)
- fix: duplicate test output for multi-line specs in spec reporter (#1006)
- fix: gracefully exit on SIGINT (#1063)
- fix expose the specified ui only in the browser (#984)
- fix: ensure process exit code is preserved when using –no-exit (#1059)
- fix: return true from window.onerror handler (#868)
- fix: xunit reporter to use process.stdout.write (#1068)
- fix: utils.clean(str) indentation (#761)
- fix: xunit reporter returning test duration a NaN (#1039)
1.15.1 / 2013-12-03
- fix: recompiled for missed changes from the last release
1.15.0 / 2013-12-02
- add:
--no-exit
to prevent process.exit()
(#1018)
- fix: using inline diffs (#1044)
- fix: show pending test details in xunit reporter (#1051)
- fix: faster global leak detection (#1024)
- fix: yui compression (#1035)
- fix: wrapping long lines in test results (#1030, #1031)
- fix: handle errors in hooks (#1043)
1.14.0 / 2013-11-02
- add: unified diff (#862)
- add: set MOCHA_COLORS env var to use colors (#965)
- add: able to override tests links in html reporters (#776)
- remove: teamcity reporter (#954)
- update: commander dependency to 2.0.0 (#1010)
- fix: mocha –ui will try to require the ui if not built in, as –reporter does (#1022)
- fix: send cursor commands only if isatty (#184, #1003)
- fix: include assertion message in base reporter (#993, #991)
- fix: consistent return of it, it.only, and describe, describe.only (#840)
1.13.0 / 2013-09-15
- add: sort test files with –sort (#813)
- update: diff depedency to 1.0.7
- update: glob dependency to 3.2.3 (#927)
- fix: diffs show whitespace differences (#976)
- fix: improve global leaks (#783)
- fix: firefox window.getInterface leak
- fix: accessing iframe via window[iframeIndex] leak
- fix: faster global leak checking
- fix: reporter pending css selector (#970)
1.12.1 / 2013-08-29
- remove test.js from .gitignore
- update included version of ms.js
1.12.0 / 2013-07-01
- add: prevent diffs for differing types. Closes #900
- add
Mocha.process
hack for phantomjs
- fix: use compilers with requires
- fix regexps in diffs. Closes #890
- fix xunit NaN on failure. Closes #894
- fix: strip tab indentation in
clean
utility method
- fix: textmate bundle installation
1.11.0 / 2013-06-12
- add –prof support
- add –harmony support
- add –harmony-generators support
- add “Uncaught “ prefix to uncaught exceptions
- add web workers support
- add
suite.skip()
- change to output # of pending / passing even on failures. Closes #872
- fix: prevent hooks from being called if we are bailing
- fix
this.timeout(0)
1.10.0 / 2013-05-21
- add add better globbing support for windows via
glob
module
- add support to pass through flags such as –debug-brk=1234. Closes #852
- add test.only, test.skip to qunit interface
- change to always use word-based diffs for now. Closes #733
- change
mocha init
tests.html to index.html
- fix
process
global leak in the browser
- fix: use resolve() instead of join() for –require
- fix: filterLeaks() condition to not consider indices in global object as leaks
- fix: restrict mocha.css styling to #mocha id
- fix: save timer references to avoid Sinon interfering in the browser build.
1.9.0 / 2013-04-03
- add improved setImmediate implementation
- replace –ignore-leaks with –check-leaks
- change default of ignoreLeaks to true. Closes #791
- remove scrolling for HTML reporter
- fix retina support
- fix tmbundle, restrict to js scope
1.8.2 / 2013-03-11
- add
setImmediate
support for 0.10.x
- fix mocha -w spinner on windows
1.8.1 / 2013-01-09
- fix .bail() arity check causing it to default to true
1.8.0 / 2013-01-08
- add Mocha() options bail support
- add
Mocha#bail()
method
- add instanceof check back for inheriting from Error
- add component.json
- add diff.js to browser build
- update growl
- fix TAP reporter failures comment :D
1.7.4 / 2012-12-06
- add total number of passes and failures to TAP
- remove .bind() calls. re #680
- fix indexOf. Closes #680
1.7.3 / 2012-11-30
- fix uncaught error support for the browser
- revert uncaught “fix” which breaks node
1.7.2 / 2012-11-28
- fix uncaught errors to expose the original error message
1.7.0 / 2012-11-07
- add
--async-only
support to prevent false positives for missing done()
- add sorting by filename in code coverage
- add HTML 5 doctype to browser template.
- add play button to html reporter to rerun a single test
- add
this.timeout(ms)
as Suite#timeout(ms). Closes #599
- update growl dependency to 1.6.x
- fix encoding of test-case ?grep. Closes #637
- fix unicode chars on windows
- fix dom globals in Opera/IE. Closes #243
- fix markdown reporter a tags
- fix
this.timeout("5s")
support
1.6.0 / 2012-10-02
- add object diffs when
err.showDiff
is present
- add hiding of empty suites when pass/failures are toggled
- add faster
.length
checks to checkGlobals()
before performing the filter
1.5.0 / 2012-09-21
- add
ms()
to .slow()
and .timeout()
- add
Mocha#checkLeaks()
to re-enable global leak checks
- add
this.slow()
option [aheckmann]
- add tab, CR, LF to error diffs for now
- add faster
.checkGlobals()
solution [guille]
- remove
fn.call()
from reduce util
- remove
fn.call()
from filter util
- fix forEach. Closes #582
- fix relaying of signals [TooTallNate]
- fix TAP reporter grep number
1.4.2 / 2012-09-01
- add support to multiple
Mocha#globals()
calls, and strings
- add
mocha.reporter()
constructor support [jfirebaugh]
- add
mocha.timeout()
- move query-string parser to utils.js
- move highlight code to utils.js
- fix third-party reporter support [exogen]
- fix client-side API to match node-side [jfirebaugh]
- fix mocha in iframe [joliss]
1.4.1 / 2012-08-28
- add missing
Markdown
export
- fix
Mocha#grep()
, escape regexp strings
- fix reference error when
devicePixelRatio
is not defined. Closes #549
1.4.0 / 2012-08-22
- add mkdir -p to
mocha init
. Closes #539
- add
.only()
. Closes #524
- add
.skip()
. Closes #524
- change str.trim() to use utils.trim(). Closes #533
- fix HTML progress indicator retina display
- fix url-encoding of click-to-grep HTML functionality
1.3.2 / 2012-08-01
- fix exports double-execution regression. Closes #531
1.3.1 / 2012-08-01
- add passes/failures toggling to HTML reporter
- add pending state to
xit()
and xdescribe()
[Brian Moore]
- add the @charset “UTF-8”; to fix #522 with FireFox. [Jonathan Creamer]
- add border-bottom to #stats links
- add check for runnable in
Runner#uncaught()
. Closes #494
- add 0.4 and 0.6 back to travis.yml
- add
-E, --growl-errors
to growl on failures only
- add prefixes to debug() names. Closes #497
- add
Mocha#invert()
to js api
- change dot reporter to use sexy unicode dots
- fix error when clicking pending test in HTML reporter
- fix
make tm
1.3.0 / 2012-07-05
- add window scrolling to
HTML
reporter
- add v8
--trace-*
option support
- add support for custom reports via
--reporter MODULE
- add
--invert
switch to invert --grep
matches
- fix export of
Nyan
reporter. Closes #495
- fix escaping of
HTML
suite titles. Closes #486
- fix
done()
called multiple times with an error test
- change
--grep
- regexp escape the input
1.2.2 / 2012-06-28
1.2.1 / 2012-06-25
- Added
this.test.error(err)
support to after each hooks. Closes #287
- Added: export top-level suite on global mocha object (mocha.suite). Closes #448
- Fixed
js
code block format error in markdown reporter
- Fixed deprecation warning when using
path.existsSync
- Fixed –globals with wildcard
- Fixed chars in nyan when his head moves back
- Remove
--growl
from test/mocha.opts. Closes #289
1.2.0 / 2012-06-17
- Added
nyan
reporter [Atsuya Takagi]
- Added
mocha init <path>
to copy client files
- Added “specify” synonym for “it” [domenic]
- Added global leak wildcard support [nathanbowser]
- Fixed runner emitter leak. closes #432
- Fixed omission of .js extension. Closes #454
1.1.0 / 2012-05-30
- Added: check each
mocha(1)
arg for directories to walk
- Added
--recursive
[tricknotes]
- Added
context
for BDD [hokaccha]
- Added styling for new clickable titles
- Added clickable suite titles to HTML reporter
- Added warning when strings are thrown as errors
- Changed: green arrows again in HTML reporter styling
- Changed ul/li elements instead of divs for better copy-and-pasting [joliss]
- Fixed issue #325 - add better grep support to js api
- Fixed: save timer references to avoid Sinon interfering.
1.0.3 / 2012-04-30
- Fixed string diff newlines
- Fixed: removed mocha.css target. Closes #401
1.0.2 / 2012-04-25
- Added HTML reporter duration. Closes #47
- Fixed: one postMessage event listener [exogen]
- Fixed: allow –globals to be used multiple times. Closes #100 [brendannee]
- Fixed #158: removes jquery include from browser tests
- Fixed grep. Closes #372 [brendannee]
- Fixed #166 - When grepping don’t display the empty suites
- Removed test/browser/style.css. Closes #385
1.0.1 / 2012-04-04
- Fixed
.timeout()
in hooks
- Fixed: allow callback for
mocha.run()
in client version
- Fixed browser hook error display. Closes #361
1.0.0 / 2012-03-24
- Added js API. Closes #265
- Added: initial run of tests with
--watch
. Closes #345
- Added: mark
location
as a global on the CS. Closes #311
- Added
markdown
reporter (github flavour)
- Added: scrolling menu to coverage.html. Closes #335
- Added source line to html report for Safari [Tyson Tate]
- Added “min” reporter, useful for
--watch
[Jakub Nešetřil]
- Added support for arbitrary compilers via . Closes #338 [Ian Young]
- Added Teamcity export to lib/reporters/index [Michael Riley]
- Fixed chopping of first char in error reporting. Closes #334 [reported by topfunky]
- Fixed terrible FF / Opera stack traces
0.14.1 / 2012-03-06
- Added lib-cov to .npmignore
- Added reporter to
mocha.run([reporter])
as argument
- Added some margin-top to the HTML reporter
- Removed jQuery dependency
- Fixed
--watch
: purge require cache. Closes #266
0.14.0 / 2012-03-01
- Added string diff support for terminal reporters
0.13.0 / 2012-02-23
- Added preliminary test coverage support. Closes #5
- Added
HTMLCov
reporter
- Added
JSONCov
reporter [kunklejr]
- Added
xdescribe()
and xit()
to the BDD interface. Closes #263 (docs * Changed: make json reporter output pretty json
- Fixed node-inspector support, swapped
--debug
for debug
to match node.
needed)
Closes #247
0.12.1 / 2012-02-14
- Added
npm docs mocha
support [TooTallNate]
- Added a
Context
object used for hook and test-case this. Closes #253
- Fixed
Suite#clone()
.ctx
reference. Closes #262
0.12.0 / 2012-02-02
- Added .coffee
--watch
support. Closes #242
- Added support to
--require
files relative to the CWD. Closes #241
- Added quick n dirty syntax highlighting. Closes #248
- Changed: made HTML progress indicator smaller
- Fixed xunit errors attribute [dhendo]
0.10.2 / 2012-01-21
- Fixed suite count in reporter stats. Closes #222
- Fixed
done()
after timeout error reporting [Phil Sung]
- Changed the 0-based errors to 1
0.10.1 / 2012-01-17
- Added support for node 0.7.x
- Fixed absolute path support. Closes #215 [kompiro]
- Fixed
--no-colors
option [Jussi Virtanen]
- Fixed Arial CSS typo in the correct file
0.10.0 / 2012-01-13
- Added
-b, --bail
to exit on first exception [guillermo]
- Added support for
-gc
/ --expose-gc
[TooTallNate]
- Added
qunit
-inspired interface
- Added MIT LICENSE. Closes #194
- Added:
--watch
all .js in the CWD. Closes #139
- Fixed
self.test
reference in runner. Closes #189
- Fixed double reporting of uncaught exceptions after timeout. Closes #195
0.8.2 / 2012-01-05
- Added test-case context support. Closes #113
- Fixed exit status. Closes #187
- Update commander. Closes #190
0.8.1 / 2011-12-30
- Fixed reporting of uncaught exceptions. Closes #183
- Fixed error message defaulting [indutny]
- Changed mocha(1) from bash to node for windows [Nathan Rajlich]
0.8.0 / 2011-12-28
- Added
XUnit
reporter [FeeFighters/visionmedia]
- Added
say(1)
notification support [Maciej Małecki]
- Changed: fail when done() is invoked with a non-Error. Closes #171
- Fixed
err.stack
, defaulting to message. Closes #180
- Fixed:
make tm
mkdir -p the dest. Closes #137
- Fixed mocha(1) –help bin name
- Fixed
-d
for --debug
support
0.7.1 / 2011-12-22
- Removed
mocha-debug(1)
, use mocha --debug
- Fixed CWD relative requires
- Fixed growl issue on windows [Raynos]
- Fixed: platform specific line endings [TooTallNate]
- Fixed: escape strings in HTML reporter. Closes #164
0.7.0 / 2011-12-18
- Added support for IE{7,8} [guille]
- Changed: better browser nextTick implementation [guille]
0.6.0 / 2011-12-18
- Added setZeroTimeout timeout for browser (nicer stack traces). Closes #153
- Added “view source” on hover for HTML reporter to make it obvious
- Changed: replace custom growl with growl lib
- Fixed duplicate reporting for HTML reporter. Closes #154
- Fixed silent hook errors in the HTML reporter. Closes #150
0.5.0 / 2011-12-14
- Added: push node_modules directory onto module.paths for relative require Closes #93
- Added teamcity reporter [blindsey]
- Fixed: recover from uncaught exceptions for tests. Closes #94
- Fixed: only emit “test end” for uncaught within test, not hook
0.4.0 / 2011-12-14
- Added support for test-specific timeouts via
this.timeout(0)
. Closes #134
- Added guillermo’s client-side EventEmitter. Closes #132
- Added progress indicator to the HTML reporter
- Fixed slow browser tests. Closes #135
- Fixed “suite” color for light terminals
- Fixed
require()
leak spotted by [guillermo]
0.3.6 / 2011-12-09
- Removed suite merging (for now)
0.3.5 / 2011-12-08
- Added support for
window.onerror
[guillermo]
- Fixed: clear timeout on uncaught exceptions. Closes #131 [guillermo]
- Added
mocha.css
to PHONY list.
- Added
mocha.js
to PHONY list.
0.3.4 / 2011-12-08
- Added: allow
done()
to be called with non-Error
- Added: return Runner from
mocha.run()
. Closes #126
- Fixed: run afterEach even on failures. Closes #125
- Fixed clobbering of current runnable. Closes #121
0.3.3 / 2011-12-08
- Fixed hook timeouts. Closes #120
- Fixed uncaught exceptions in hooks
0.3.2 / 2011-12-05
- Fixed weird reporting when
err.message
is not present
0.3.1 / 2011-12-04
- Fixed hook event emitter leak. Closes #117
- Fixed: export
Spec
constructor. Closes #116
0.3.0 / 2011-12-04
- Added
-w, --watch
. Closes #72
- Added
--ignore-leaks
to ignore global leak checking
- Added browser
?grep=pattern
support
- Added
--globals <names>
to specify accepted globals. Closes #99
- Fixed
mocha-debug(1)
on some systems. Closes #232
- Fixed growl total, use
runner.total
0.2.0 / 2011-11-30
- Added
--globals <names>
to specify accepted globals. Closes #99
- Fixed funky highlighting of messages. Closes #97
- Fixed
mocha-debug(1)
. Closes #232
- Fixed growl total, use runner.total
0.1.0 / 2011-11-29
- Added
suiteSetup
and suiteTeardown
to TDD interface [David Henderson]
- Added growl icons. Closes #84
- Fixed coffee-script support
0.0.8 / 2011-11-25
- Fixed: use
Runner#total
for accurate reporting
0.0.7 / 2011-11-25
- Added
Hook
- Added
Runnable
- Changed:
Test
is Runnable
- Fixed global leak reporting in hooks
- Fixed: > 2 calls to done() only report the error once
- Fixed: clear timer on failure. Closes #80
0.0.6 / 2011-11-25
- Fixed return on immediate async error. Closes #80
0.0.5 / 2011-11-24
- Fixed: make mocha.opts whitespace less picky [kkaefer]
0.0.4 / 2011-11-24
- Added
--interfaces
- Added
--reporters
- Added
-c, --colors
. Closes #69
- Fixed hook timeouts
0.0.3 / 2011-11-23
- Added
-C, --no-colors
to explicitly disable
- Added coffee-script support
0.0.2 / 2011-11-22
- Fixed global leak detection due to Safari bind() change
- Fixed: escape html entities in Doc reporter
- Fixed: escape html entities in HTML reporter
- Fixed pending test support for HTML reporter. Closes #66
0.0.1 / 2011-11-22
- Added
--timeout
second shorthand support, ex --timeout 3s
.
- Fixed “test end” event for uncaughtExceptions. Closes #61
0.0.1-alpha6 / 2011-11-19
- Added travis CI support (needs enabling when public)
- Added preliminary browser support
- Added
make mocha.css
target. Closes #45
- Added stack trace to TAP errors. Closes #52
- Renamed tearDown to teardown. Closes #49
- Fixed: cascading hooksc. Closes #30
- Fixed some colors for non-tty
- Fixed errors thrown in sync test-cases due to nextTick
- Fixed Base.window.width… again give precedence to 0.6.x
0.0.1-alpha5 / 2011-11-17
- Added
doc
reporter. Closes #33
- Added suite merging. Closes #28
- Added TextMate bundle and
make tm
. Closes #20
0.0.1-alpha4 / 2011-11-15
- Fixed getWindowSize() for 0.4.x
0.0.1-alpha3 / 2011-11-15
- Added
-s, --slow <ms>
to specify “slow” test threshold
- Added
mocha-debug(1)
- Added
mocha.opts
support. Closes #31
- Added: default [files] to test/*.js
- Added protection against multiple calls to
done()
. Closes #35
- Changed: bright yellow for slow Dot reporter tests
0.0.1-alpha1 / 2011-11-08
0.0.1-alpha1 / 2011-11-08


Code generator for AVS Authentication
Welcome to the inital code generator for MMM-Alexa
This generator will allow to link MMM-Alexa to your amazon account.
It will return the initial code for your module configuration (InitialCode).
You can get support in 4th Party modules