on fbfa2ea help sign in
fbfa2eaBump version bound for megaparsec (stay at major release 5)3noch 3356ff7Drop uuid-aeson in favor of aeson >= 1.13noch c7a5965Merge branch 'master' of https://github.com/agentm/project-m36AgentM cf9eaf0fix hlint cpp-define needed for lintingAgentM 1c8c3aaMerge pull request #135 from 3noch/patch-1AgentM d0fbb52Fix indentation of usage descriptionsElliot Cameron 1f502edadd blog example sourceAgentM 12c2953add blog + comment exampleAgentM 83d8a04add toDefineExpr to Tupleable to cut down on boilerplate rv creationAgentM 83f8002rename ambiguously-named toDatabaseExpr to toAddTypeExprAgentM a8fc801Merge branch 'master' of https://github.com/agentm/project-m36AgentM f1eb2deuse cabal's package version macro instead of our ownAgentM 9d24a9caddress hlint suggestionsAgentM 06aea4bfix GHC 7.10 getCurrentTime sourceAgentM 9da577dupdate Tupleable test to account for fromTuple signature changeAgentM dcac4deadd Tupleable typeclass documentationAgentM 63affe5add round-trip marshaling to OutOfTheTarpit example adjust type fromTuple :: Either RelationalError aAgentM 103bcacdelintifyAgentM f87f0eeupdate OutOfTheTarpit example to demonstrate Tupleable useAgentM 8e1cdf8add renaming if necessary to attributes in foreign key generationAgentM adee926fix insufficient laziness in :*: Tupleable matching add test exercising undefined exceptionAgentM c413bf0WIP compilation checkpoint toAttributesG is causing "toAttributes (undefined :: Test)" to be evaluatedAgentM 42746d8non-compiling tupleable implementation I need some assistance to fix fromTupleG in the Selector caseAgentM c60eed4WIP Tupleable typeclassAgentM b5ef26aincrement db format version due to addition of timestamps improve validation of on-disk database format resolves #133AgentM d0a221ffix GHC 7.10 build warnings/errorAgentM fc9e67afix failure to jump to proper head after automergetohead resolves #131AgentM 977e1bcadd :automergetohead command to tutdAgentM fe6bcd5fix hlint complaintAgentM f2fc60cfix interval overlap detectionAgentM 9f743caMerge branch '120_fix_interval' into 123_commit_timestampsAgentM 2aba32aadd commit timestamps the timestamp is from the start of the transaction creation, not when it is committed (a few milliseconds later typically)- this is identical to postgresql's now() stamp resolves #123AgentM 797dd93update docs with data type constructor informationAgentM 40e1d8aswitch from makeByteString to bytestring constructor this makes the bytestring constructor more in line with other non-primitive constructor functionsAgentM c4193derestore interval data type all tests passing resolves #120AgentM deb38d8allow cassava 0.5 tested both 0.4.5.1 and 0.5.0.0AgentM 79f6900fix leftover hlint suggestions due to merge conflictsAgentM 5191549Merge branch '127_hlint'AgentM eba87c2remove non-compiling and stale Interval type parserAgentM 989bb3bremove stale/unused TutorialD datetime parser (users should use the atom function constructor instead)AgentM 205293afix hlint command line invocation references #127AgentM 1907adfsupport previous version of cassava for building with stackage LTS resolves #129AgentM 94a837eRevert "upgrade megaparsec to 6.0.2 in preparation for GHC 8.2.1 support"AgentM e1a7a61add hlint to travis configurationAgentM b27ae9ffix or squelch all hlint hints in src, examples, test directoriesAgentM 00c9dc73noch found that automerge was not writing all new transactions to disk this was caused by the transaction graph persistence optimization which assumed writing only the latest heads was safe this has been replaced by commit infrastructure being explicit about which transactions it has added to the graph this is potentially a further optimization since it shouldn't need to check the filesystem for which heads have already been written resolves #128AgentM 75dd04cdisable ghc-8.2.1 building some dependencies don't yet build with GHC 8.2.1, so it's pointlessAgentM 4bab741upgrade megaparsec to 6.0.2 in preparation for GHC 8.2.1 supportAgentM 7b2ef25cleanup GHC warningsAgentM e04c0ddudpate to cassava 0.5AgentM