#evehq

There's also 'metadata' support we could use: http://docs.sqlalchemy.org/en/rel_0_8/core/sche...

And... I'm not sure what to do about embedded dictionaries as used in the eve-demo's people.location schema entry...

Do we assume that all underlying db schema have been created externally, or must we offer some way of creating the schema?

Eve will create the collection/documents if they are missing, but mongodb makes that a trivial task. Hard to replicate that in the SQL world.

I'd say assume the schema exist already

I think that's a good first step. We can ask SQLAlchemy to verify, I think.

even for mongodb it doesn't really make sense. You want to optimize the DB, make sure you have the needed indexes, etc.

True enough.

I'll assume we should raise an exception during init if something's amiss

agreed

What about constructs like people.location? Not sure if we're expected to translate that into SQL...

(complex, nested data types)

I guess a first attempt at SQL could get away with raising an exception :)

I'm good with that - another thing to check at init-time, I suppose.

Should we have another custom exception or recycle someone else's? InvalidSchemaException() ?

(so many questions...)

yes for specialized exceptions

and questions are good to have :)

I need feedback on this if you have a couple minutes guys https://github.com/nicolaiarocci/eve/issues/23

I've no opinion on the events question.

it's alright :)

At least not this morning. :-/

I don't know what kind of use cases you're trying to address.

that's actually a feature request (not mine), but there might be some interesting use cases

like custom logging or custom notification etc

not to mention updating other databases/apis

I prefer max flexibility/granularity, natch, and I'd prefer to see headers and such passed to the callback... but lacking use cases I don't know if that's reasonable. I'll try to check out the original feature request...

yes I'll go with on_getting()/on_get() etc

(beware, I have to fight the urge to over-engineer... Simple is better than complex. Complex is better than complicated. 8-)

well that's one case where simplicity for the API (just two events) would imply complexity on the calling script (parse request method, decide what to do etc). Of course I could also provide both class of events, leaving the client decide to which to subscribe… hmmm

*both classes of event

*both event classes :D

I'm all for flexibility - should I leave these comments on github rather than here? You asked for feedback there...

yeah please do, will encourage discussion

thanks

Ok, done. Bombs away!

That's me, Mr. Opinion. Worth every centisimi

or is that centisimo?

My brain hurts

centesimi (plural) / centesimo (singular)

ah, yes, thanks

another copy and paste failure :-/

btw, I notice that Eve.validate_schema() provides incomplete 'offender' data if there are multiple offending entries in the schema -- last one wins.

Minor issue but it might cause confusion. I like to collect problems in a list and carry them around in my back pocket.

hmm will check, shouldn't do that

I've not tested it but the code says it will.

If both eve.DATE_CREATED and eve.ID_FIELD are in schema, only ID_FIELD will be used in message?

Unless I misread that logic.

And if I did, I probably ought to go hide in the corner.

ah yes I didn't get the context

(was thinking about payload validation)

(Very minor issue)

I assume one goal of Eve is to provide a friendly framework for building REST interfaces in Flask, so ... I like friendly.

I created an issue in the queue...

ok

I may submit a pull request for consideration when I have time

sure

Probably should delegate schema validation to the data instance...

but we can do that implicitly in the DataLayer constructor, I suppose

in activist yes, validate_schema could/should behave like the domain validator (cerberus), reporting a list of errors

will fix

or are you going to send a PR for that?

Hello

howdy AndrewK

I sent you a brief email the other day concerning 404 on posting from a client I am trying to test.

ah yes, I remember that one

did you figure it out?

If you aren't terribly busy, do you think you could assist me in figuring out the problem?

give me a few minutes

brb

negative. I was hoping it was because I was running it from windows. But after starting it up on a linux vm and testing your eve-demo-client against it, it works. It still 404's from my other 'clients' post request.

no problem

:)

mmm love seeing those commits

where/what file can I start tracing to track down where I am getting a 405 even though my endpoints have all methods turned on?

Are you getting them on specific endpoints or all of them? Are you getting them with specific methods or all of them?

PATCH

i verify all methods (for tracking down) are turned on..

what kind of client setup are you using?

curl or something else

test_client

once app is running

where is first entry point for receiving request

then I can trace from there

i use wingware

ide

just realized that project was using global werkzeug

not virtualenv

yep

i was trying to jump into venv but it was not going there

ah

i now notice werkzeug.__file__ is pointing to global :(

i was looking through source to help, as I have just started trying to test things with Eve two days ago. :)

i love what nicola has put together

i love how robust it is, even if it is quite young.

i do some extra magic and so rather than import his package, i am following his pattern

currently focussed on CORS and auth

i dont do much in python, but the appeal of eve intrigued me.

CORS support is key IMHO

is CORS support a WIP for eve or is it already there?

WIP?

work in progress, sorry.

he just implimented

AndrewK, I'm ready

ah

i am working to wire it up to an AngularJS client on external domain

hello nicola

I was hoping yours was a windows issue too :D guess not

haha nope.

anywho, i think its specific to my client attemps

attempts*

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <title>404 Not Found</title> <h1>Not Found</h1> <p>The requested URL was not found on the server.</p><p>If you entered the URL manually please check your spelling and try again.</p> GET /people/ HTTP/1.1 Host: 192.168.1.199 User-Agent: LiveCode (Win32) HTTP/1.0 404 NOT FOUND Content-Type: text/html Content-Length: 238 Server: Eve/0.0.4 Werkzeug/0.8.3 Python/2.7.3 Date: Fri,

ew that lost its formatting

one moment

got it

what's the request like?

I see /people/

i used your eve-demo and eve-demo-client

and both work well

i can browse to the resources and tings are fine from my browser

even /people/ endpoint working fine from broswer?

I am using livecode from http://runrev.com to try and access the basics.

yep

see the data just fine

albiet in xml instead of json

yes that's right

don't you love that xml of mine? took a hell of a lot of work to get it right, goddamit :)

i was trying to post your demo json to the api from livecode

it failed with a 404

then i just tried doing a get

does the same thing

the response is first in that paste

then the headers I sent

then the headers i recieved back

seems pretty standard, but it doesnt seem to be doing much that the browser version of the get isnt doing