wingechr
wingechr
both tables and column names now must adhere to the regexp `^[a-z][a-z0-9_]{0,MAX_IDENTIFIER_LENGTH-1}$`, `MAX_IDENTIFIER_LENGTH` currently being 50. The length limit is a little shorter than the postgres restrictions (63 for tables,...
for table names, this is already implemented `actions.py` `assert_valid_table_name(table)`: ```python ... if not re.match(r"[a-z][a-z0-9_]*", table): raise APIError ``` but not for column names. columns names must probably checked in 2...
@han-f let's have a look at this together. there is probably a way to make it look better using styling options.
yea. my suggestion is to NOT show the resource section from the metadata. @jh-RLI, @Ludee what do you think?
if it's not open data, it should not be on the oep, right?
in theory, you should be able to nest the functions like this, but i have not tested it: ```python data = { "query": { "fields": [ { "type": "function", "function":...
I don't mind doing it this way (add it as comment first). reduces the chance of breaking things
@MGlauer, @Bachibouzouk I would be happy to do that. Unfortunately, in the current development branch (f786c2502bbb), insertion of data via REST API seems to be broken. The error thrown is...
@Ludee are you SURE this was ever possible?? From what I can see, this would have to be in `oeplatform/dataedit/static/dataedit/backend.js`, with some api call bound to events in the jquery.DataTable...
fixed on most of the jupyter tutorials